IT Services
UI/UX Design Services in Nepal
A design is finished when a developer can build it without asking questions. We deliver flows, states and a component system - not a folder of beautiful screens that describe only the happy path.
Most design handovers fail in the same place: the empty state, the error, the loading moment, the row of text three times longer than the mock. Those are the screens users spend real time in. We draw them, name them, and put them in the same file as the rest, which is why our handovers do not generate a fortnight of clarification calls.
What ui/ux design covers here
Discovery and user flows
Who uses this, what they came to do, and the shortest honest path to it. Mapped as flows before anything is drawn, so structural mistakes get caught while they are still cheap.
Wireframes and prototypes
Low-fidelity first, then a clickable prototype you can put in front of five real users. Testing a prototype costs a day and routinely saves a month.
High-fidelity interface design
Every screen at mobile and desktop widths, with the loading, empty, error and permission-denied states drawn rather than assumed.
A design system, not a style guide
Type scale, colour tokens, spacing, and the actual components - buttons, inputs, tables, modals - with their states. Handed over in Figma with the tokens named the way the code will name them.
Accessibility as a requirement
Contrast checked against WCAG AA, hit targets sized for thumbs, focus order that works on a keyboard, and labels on every control. Built in from the start, because retrofitting it is a redesign.
What you receive
- Figma file with organised pages, components and variables
- Clickable prototype for the primary flows
- Every screen at 390px and 1440px minimum
- Design tokens exported for Tailwind or CSS variables
- A handover walkthrough with the build team
How a project runs
- 1
Talk
A conversation about the problem, not a feature list. We ask what happens today, who does it, and what it costs when it goes wrong.
- 2
Scope
A written scope with phases, what is explicitly out, and a price against each phase. You can take this document to another firm - that is fine, and it means you are comparing like with like.
- 3
Build
Fortnightly demos on real data. You see progress in the working thing, not in a percentage on a chart.
- 4
Launch
Staging first, a rehearsed cutover, and someone watching for the first days. Redirects, certificates and DNS handled by us.
- 5
Support
A handover you can act on, and a maintenance option if you want us to keep watching. Not compulsory.
Questions we get asked
Can you design for a build we already have?
Yes. A redesign on top of a working product is usually the highest-return design work there is, because the hard part - knowing what people actually do - is already answered by your data.
Do you do logos and brand identity?
We do brand application: how the identity behaves in a product, its type, colour and iconography. A full identity programme from scratch is a different discipline and we will tell you when you want that instead.
Will you also build it?
Usually yes, and it is cheaper when we do - no translation loss between the file and the code. But we hand over to in-house teams regularly, and the deliverable is written to be built by someone else.
How many revision rounds are included?
Two structured rounds per milestone, which is enough when the flows were agreed first. Unlimited revisions sound generous and in practice just mean the direction was never settled.
Often bought together
Everything we build can be deployed straight onto AstraCloud hosting or a VPS, in Nepal or internationally, with SSL, backups and the control panel already configured. You are not obliged to host with us, and the price of the build does not change either way.
Talk to us about ui/ux design
Tell us what the problem is and we will tell you what it takes to fix it - including when the answer is that you do not need us.
No form to fill in - the chat opens in this window and reaches our team directly.