Product design starts with flows, not screens: who this person is, what they are trying to finish, and where they usually give up. We describe the main flows first and draw afterwards.
Then we lay out every key screen in the states teams normally forget: empty list, loading, network error, a name that is too long. Those are exactly the states a developer otherwise invents alone, and that is where products drift apart.
You end up with a design system in Figma: components, tokens, grid. A developer assembles new screens from it without asking a designer about every button.
What you receive
- Flow map and product structure
- Key screens for desktop and mobile
- States: empty, loading, error, extreme values
- Figma design system with components and tokens
- Clickable prototype of the main flow
- Developer handoff with specifications
Frequently asked
UI/UX design for a product
01Will you build it afterwards as well?
We can. Mobile app and web platform are separate entries in the catalog. The files are not locked to us and any team can build from them.
02Do you work in Figma?
Yes. You get access to the file and remain its owner.
Related services
DesignBusiness card design
A double sided, print ready business card in one to two working days.
UZS 120 000
1–2
working days
DesignSocial media design pack
Ten finished posts and story templates in one system, with editable sources.
UZS 850 000
3–5
working days
DesignPitch deck design
Up to fifteen slides, built to be read rather than admired.
UZS 1 400 000
4–7
working days
