UI and UX Design
Design that survives contact with real users
Most software is not hard to use because nobody designed it. It is hard to use because the design was approved in a meeting by people who already knew how it worked. We design for the person seeing it for the first time, on a mid range Android phone, in a hurry.
- Tested with real users, not just reviewed internally
- Handover a developer can build from without asking
- Works on the devices your customers actually own
Dashboards and admin panels
Ecommerce and checkout
User research and testing
Design systems
Three ways design goes wrong, and they are all avoidable
None of these are about taste. They are about process, and each one is visible before a line of code is written.
It was never shown to a user
The team reviewed it, the client approved it, and nobody outside the room tried to complete a task with it. The first real feedback arrives after launch, when changing it is expensive.
It was designed on a desktop
Most of your customers are on a phone, often on mobile data, often with one hand. A layout that only holds together at 1440 pixels wide fails where the traffic actually is.
The handover is a picture
A flat image with no spacing values, no states, no error cases. The developer guesses, the result drifts from the design, and everyone blames the other side.
A handover a developer can build from without asking questions
Research findings
Interviews with your actual users or staff, what they are trying to do, and where the current process breaks. Written plainly, five pages rather than fifty.
User flows
Every path through the product, including the ones that fail. What happens with no results, no connection, an expired session, a declined payment.
Wireframes
Structure before decoration, so the arguments about layout happen while changes are cheap.
Visual design
Every screen at mobile and desktop width, in light and dark where the product needs both.
A design system
Colour, type scale, spacing, buttons, forms, tables, empty and error states, defined once and reused. This is what keeps the product consistent after we leave.
Developer handover
Measurements, assets, states and behaviour notes. A build ready file, not a screenshot.
Four phases, each ending in something you can look at
Understand, week 1
We talk to the people who will use this and the people who support it today. We read your support messages. We look at what you already have and what the numbers say about where people give up.
Structure, weeks 2 to 3
Flows and wireframes. Deliberately unstyled, because this is the stage for deciding what goes where, and colour is a distraction from that.
Design, weeks 4 to 6
Visual design and the system behind it. Two review rounds are included, with one named approver on your side so feedback does not contradict itself.
Test and hand over, weeks 7 to 8
A clickable prototype put in front of five to eight real users. We fix what they struggle with, then hand over to your developers or ours.
Five users will find most of your problems
Usability testing has a reputation for being expensive and slow. At the scale most businesses need, it is neither.
You do not need a lab
A quiet room, a phone, a prototype and somebody who matches your customer. Watch them try to finish a task without helping. The first two sessions usually change the design.
Test on the real device
In Pakistan that means a mid range Android on mobile data, not the latest iPhone on office WiFi. Load time and touch target size stop being theoretical very quickly.
Watch, do not ask
What people say they would do and what they actually do are different. Give them a task and stay quiet, however uncomfortable it gets.
Urdu and English both
If your users mix languages, your interface needs to work when they do. Labels, placeholders and error messages all behave differently in practice than they do in a design file.
What clients ask before starting
How much does UI and UX design cost in Pakistan?
For a focused product, typically 250,000 to 700,000 PKR covering research, flows, design and a handover file. Large multi role platforms run higher, driven by the number of user types rather than the number of screens.
How long does it take?
Six to eight weeks for a standard product. Faster if the requirements are settled and you have one decision maker, slower if we are still deciding what the product is.
Can you design for a product we already have?
Yes, and it is often the higher return work. A redesign grounded in where existing users actually give up beats a new product built on assumptions.
Do you build what you design?
We can, and we are happy not to. The handover is written so any competent front end team can build from it. If you have developers, use them.
What if we do not know what we want yet?
That is what the first phase is for. Come with the problem rather than the solution, and expect the first two weeks to change your mind about something.
Tell us what people are struggling to do
Not what you want built. What your customers or your staff are trying to get done, and where it currently goes wrong. That is enough for us to tell you honestly what design work would help and what it would cost.