Frame the problem and constraints
I identify the users, decisions, content, technical boundaries, and evidence available before choosing a visual direction.
A process that connects product decisions to working software.
The exact depth changes by project, but the sequence stays grounded in scope, structure, implementation, and verifiable quality.
Structure flows and information
I translate ambiguity into journeys, priorities, navigation, data relationships, and screen states that make the product understandable.
Design and build the system
I create reusable visual and interaction patterns, then connect them to responsive frontend state, APIs, or persistence according to the product scope.
Validate, document, and ship
I test critical journeys, responsive behavior, language direction, state transitions, and deployment readiness, then document limitations honestly.