years of experiences design & software

this is where i start with the people first; i sit with the problem before i sit with the pixel, mapping what they actually need and what the business actually wants, then shaping the flow, the screens, and the small details until the thing feels obvious to use; i build the design system too, so what we make can keep growing without losing its own face

i build for the platform in its own language; swift for iOS, kotlin for android, so the app moves the way the device expects and nothing feels borrowed; i care about the parts users never name — how fast it opens, how it behaves with no signal, how it holds their data safely — because that is what makes an app trusted, not the splash screen

the web is where most people meet you first, so i treat it as the front door; i turn design into markup that is fast, accessible, and honest to the layout, and i keep it working on the phone in someone hand as much as on the big screen; performance is not a step at the end for me, it is part of how i build from the first line

when a team needs to be on both platforms without building everything twice, this is the path i take; one codebase, and still a product that feels right on each side; i use it when the trade is worth it and i say so when it is not — because choosing the right tool is part of the job, not a thing you decide before you understand the problem