Mockup, wireframe and prototype: what is the difference
A wireframe is a plain, unstyled layout that shows where blocks sit on a screen. A mockup is the finished visual design: real fonts, colours, buttons and copy. A prototype links those mockups together with transitions, so you can tap through the app the way a customer would.
This matters when you read a proposal, because designers often list these as separate stages. If you are only shown polished screens with no connections between them, you cannot see where a user might get lost.
What the design process includes
Good design starts with questions, not drawing: who is the user, what action should they complete, and what stops them today? Screens come after that.
- Brief and goals: what the app should bring the business, such as repeat orders, bookings, payments or retention.
- User flows: the path from opening the app to the key action, for example from catalogue to checkout.
- Structure and wireframes: which screens exist and how they connect.
- Visual style: colours, fonts and icons that follow your brand guidelines.
- Full mockups of every screen and state: empty cart, error, loading.
- A clickable prototype tested with real people.
- Developer handoff: sizes, spacing, files and exported graphics.
What to account for in the Uzbek market
Your audience is bilingual, so the design should handle Russian and Uzbek from the start. Words in Uzbek Latin script are often longer, and a button that fits Russian text perfectly may break with the Uzbek version. Check every screen in both languages before handoff.
The second point is familiar behaviour. Payment through Click and Payme, sign-in with a phone number and SMS code, a quick link to a manager in Telegram, choosing a district or landmark instead of typing an exact address: these belong in the mockups, not in a late patch. People used to Uzum or OLX expect similar logic and will not spend time learning a new one.
Do not forget the regions either. Connections can be unstable and phones vary widely in screen size and power, so the mockups should show slow-loading and offline states.
What you should receive at the end
The result should be an organised project any developer can pick up, not a folder of images. Ask for access to the working file, not just a PDF export.
- A Figma file with clearly named pages and layers.
- Mockups for the main screen sizes, plus separate iOS and Android versions if you launch on both.
- A component library: buttons, fields and cards in one place.
- A clickable prototype of the main user flow.
- Notes on logic that is not obvious from the screen.
- Rights to the design confirmed in the contract.
What drives the price
Cost depends first on the number of screens and how complex they are. A login form and a catalogue with filters, a map and online payment are very different amounts of work. A ready brand book, audience research, the number of revision rounds and the deadline all play a part. A firm figure is only possible after the task is discussed, so be wary of a quote that arrives without any questions for you.
Do you need an app at all
Before ordering mockups, ask honestly whether you need an app, or whether a mobile-friendly website or a Telegram bot would do. For one-off purchases and information, a website often wins: people find it through search and do not have to install anything. An app makes sense when customers return regularly, for example for orders, subscriptions or a loyalty programme.
At markdev we start with that question, and if a website solves the problem, we say so. If you are unsure about the format, talk to us about your task. We can help you choose between an app, a website and a bot, and prepare a clear brief for whichever you pick.
FAQ
How is a mockup different from a prototype?
A mockup is the finished visual design of individual screens. A prototype connects those screens with transitions so you can walk through the user journey as in a real app.
Which tool is best for app mockups?
Figma is the most common choice. It runs in the browser and makes revisions and developer handoff simple. What matters is that you get access to the source file.
Do I need separate mockups for iOS and Android?
If the app launches on both, it is wise to respect each platform's interface rules for navigation, system buttons and sizing. Many screens can be shared, but the differences should be checked early.
Can I test mockups before development starts?
Yes, and you should. Show the clickable prototype to a few customers or staff and watch where they hesitate. Fixes at this stage cost the least.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.