Do you also build what you design?
Often, yes. Being the person who implements the design changes what gets designed: no state is left unexplained, and no layout is agreed that the browser cannot hold.
UI/UX design
UI/UX design in Kathmandu
I am a UI/UX designer in Kathmandu with 4+ years of interface work, from Figma systems to production screens. I design the flow first, then the screen, and I write the handoff notes, because a design that cannot be built predictably is only half a design.
Flows before pixels
The first artefact in every design engagement is not a mockup. It is a list of the decisions the user has to make and the order they make them in. Most interface problems are ordering problems: two screens doing one job, or a confirmation step nobody needs.
Only once the flow holds up does visual design start. That sequence is what stops a project from producing beautiful screens for a journey that was never going to work.
Design systems that survive the second sprint
I build in Figma with tokens: colour, spacing, radius, type steps and elevation. Components reference the tokens, so a brand change is a token change rather than a redraw. The same names then appear in the code as Tailwind theme values, which is why the design and the build stay in step after the first release.
Accessibility is part of the system, not a later audit: contrast checked against the palette, focus states designed rather than defaulted, and every interactive element reachable by keyboard and describable by a screen reader.
Handoff, prototypes and honest scope
Handoff is a deliverable: named components, states for empty, loading and error, and notes on the behaviour that a static frame cannot show. Where motion carries meaning, I prototype it rather than describing it in a comment.
I also design in scope. A five screen app and a forty screen platform are different projects, and the design approach for the first should not pretend to be the second.
How the process runs
- 01Interviews or a working session to understand the decision the user is trying to make
- 02Flow map and screen inventory, agreed before visual work starts
- 03Wireframes for the two or three screens that carry the product
- 04Visual design on a token system, with states for empty, loading and error
- 05Handoff: named components, behaviour notes, prototypes for anything animated
How pricing works
Priced per project from the screen count and the number of user roles, or per design sprint if the product is still finding its shape. Brand identity work is scoped separately, because it is a different discipline and it deserves its own estimate rather than being folded into the interface budget.
Questions about ui/ux design
Can you work with our existing brand?
Yes. I extend an existing brand into a product design system rather than replacing it, and I will flag the places where the brand does not survive contact with a working interface.
Do you run user testing?
I run lightweight tests: five users on the key flow, watching for hesitation rather than asking for opinions. For heavier research I bring in the methods the decision actually needs and say when something is beyond what I can claim.
Open for projects, collaborations and virtual coffee chats. Send the technical requirements, Figma drafts, or napkin sketch, and I will reply with an architectural breakdown, realistic milestone roadmap, and high-impact execution plan.