Direction & flows
Content structure, user journeys and wireframes before diving into visual details.
I start with the problem, the people and the priorities. I design flows and interfaces that make products clearer, then use prototypes to test the decisions. Knowing how things are built keeps my design grounded.
UX/UI / Figma / PrototypingHave an idea to clarify, a website to rethink or a product that should be simpler?
Let’s talk ↗Content structure, user journeys and wireframes before diving into visual details.
Responsive screens, clear hierarchy and interactive prototypes to explore the product.
Documented components, typography, colors and states to connect design with development.
From words to work

A fashion app concept that started as wardrobe management and was narrowed into a virtual try-on MVP, combining UX research, brand direction, mobile UI, and React Native development.

An open-source financial OS that combines data, automation, and AI agents to make personal finance operational.
Every project changes the starting point. The approach stays the same: clarify, build, collaborate and refine.
We start with people, content and goals. A new layout only makes sense when we know what it should make easier.
I organize information, flows and wireframes. We explore the structure before investing in visual details.
Typography, color, components and states become a coherent system. The prototype makes decisions navigable, not just attractive.
I refine responsive views and document behavior. I can support the developer or take the design into frontend implementation myself.
The care stays the same. How we organize the work changes around what the project needs.
We define goals, starting materials and outputs. I can own this discipline or connect it to the others, within a clear scope.
Tell me about it ↗Frontend at the core, a design mindset and a collaborative approach. My projects show how I work; we can talk about the contribution your team needs.
Get to know me ↗Yes. We can start with its current content and journeys, understand what works and rethink the structure and interface without changing everything by default.
It depends on the project: flows, wireframes, UI, components and a prototype may all be relevant. We agree on outputs at the start so the transition to development is clear.
Yes, within an agreed scope. Design and frontend can be separate contributions or one continuous path, from structure to a working interface.