UI/UX
What dies between Figma and the Nepal site
Empty, error, loading, tiny screens.
Kathmandu UI studios still sell a ZIP of frames. A developer later invents the states. Later is where conversion dies. I design those states because I will code them. That is the UI/UX practice.
OpenListener and MayaHold are live. This site is the sample. I do not highlight UI as a colour stunt. I highlight the frontend that has to carry the file.
Graphic design is a separate year on my record. Posters are not product UI. Labels keep the work clean. Other work experience says that honestly.
UI/UX
Research, then IA, then a system
Pretty last. Meaning first.
I start with the job the visitor has. Then information architecture. Then a small system: type, space, components that repeat. Then screens. Handoff culture starts at screens and never reaches a system, so every page is a one-off.
Conversion is a sentence on the page that matches the search. SEO people who cannot change the layout will write meta and pray. I change the layout.
If your Figma has 80 artboards and no empty state, it is a pitch, not a spec.
UI/UX
How I run UI when I also ship
The designer cannot hide from the build.
I compile. Constraints show up in the week they are still cheap. A studio handoff shows up in week eight as a surprise.
Founders who want a pure UX consultancy with no code should work with that. Founders who want a landing that ranks and books should not.
Compare studios on the vs pages if you need a named contrast. This post is the method.
UI/UX
What to send instead of a ZIP
A URL, a job, a number.
Send the current site, the job a visitor is trying to finish, and the number you care about. I will tell you whether we redesign in code or keep a slice of the old IA.
Students: copy a live form, not a Dribbble card. Learn in Nepal is the classroom.
Email [email protected]. Do not attach 2GB of Figma if the origin is already the problem.