Ariena “Ari” PhannaenUX/UI · Product · UX Engineer
I work where empathy, systems thinking, and technical craft meet — taking products from research and information architecture through interface design, design systems, and working front-end prototypes. I don’t hand off mockups. I think in components, states, and transitions.
Each project is a system-level problem — multi-user healthcare triage, behavioural wellness loops, spatial learning, two-sided marketplaces, and enterprise reporting. The order below reflects how much of the thinking is documented, not how recent the work is.
Predictive petcare ecosystem connecting owners, nurses, and clinics through empathy-driven design.
Goal manifestation app turning intentions into actionable daily rituals
Digital acupuncture learning platform with 3D interactive body maps
Marketplace connecting AI startups with specialized talent and resources
Presented in full on Behance — travel insurance conversion, content navigation, and enterprise impact reporting.
I'm Ariena Phannaen, though most people call me Ari — a designer who believes great products are built at the intersection of empathy, systems thinking, and technical craft.
My work spans UX research, interface design, interaction design, and front-end prototyping. I don't just hand off mockups — I think in components, states, and transitions.
Whether it's a healthcare platform that saves lives or a wellness app that helps people grow, I approach every project with the same question: how can this be more intentional?
Pixel-level attention to visual design, interaction patterns, and accessibility. Every interface element is intentional.
I see beyond screens — mapping user journeys, business models, and technical constraints into cohesive product systems.
I speak the language of developers. State management, component architecture, and performance are part of my design process.
.png&w=3840&q=75)
Ariena “Ari” Phannaen — UX/UI, Product & UX Engineering
Every discipline below links straight to the part of a case study where that work is documented.
Motion is a communication layer, not a finish. Each pattern below states what triggers it, what it does, and the cognitive job it is doing — the same rationale I write into a spec for engineering.
Components, states, and tokens — not a screenshot of a library, but the working primitives this site is built from. It is how I hand work to engineering: every state accounted for, every value named.
I'm open to product design roles, consulting engagements, and meaningful collaborations that make a difference — particularly work where research, systems, and engineering have to meet in one person.
