First, decide whether you need an app at all
Before anyone draws a screen, check the task honestly. In many niches in Uzbekistan a Telegram bot, a lightweight website or an Instagram catalog is enough: customers are used to messaging a business and paying through Click or Payme without installing anything. An app makes sense when people come back regularly, for example to order food, book services, track a delivery, or use an account with a loyalty program.
Write the goal in one sentence tied to a result: more repeat orders, fewer calls to the front desk, bookings without staff involvement. That sentence becomes your filter. If a screen does not serve the goal, it does not belong in the app.
The brief: what to write down before the first mockup
A brief is a short written document. Without it a designer has to guess. It does not need to be a formal technical specification; that can be assembled later together with the contractor, using the brief as a base.
- Who the user is: age, habits, city or regions, comfort with smartphones.
- Key scenarios: the few actions people open the app to perform.
- Platform: iOS, Android or both. Check which phones your customers actually use.
- Interface languages: for local audiences, plan Russian and Uzbek from day one, not as a later add-on.
- Payments and integrations: Click, Payme, Uzum, CRM, accounting system, maps and geolocation.
- Budget and desired timeline, stated openly before work begins.
- References: what you like, what you dislike, and why.
Logic before looks: user flows and wireframes
The first real design work is a screen map and user flows. This is a diagram with no colors or fonts: which buttons exist, where each leads, and what a person sees when a list is empty, data is loading or something fails. Usability is built here, not while picking icons.
Next come wireframes, rough screens made of gray blocks. Their job is to confirm that the user's path makes sense while it is still cheap to change. Moving a block in a sketch takes minutes; reworking finished visuals and code takes days.
Visual style and the UI kit
Only once the skeleton is approved do color, typography, illustration and icons come in. The result is a UI kit: buttons, fields, cards and all their states, from which every screen is assembled. It keeps the interface consistent and speeds up developers.
Account for local specifics. Russian and Uzbek labels are usually longer than English ones, so buttons and cards need room to breathe. Avoid copying the interface of a big Western app: it solved other problems for another audience and ignored habits like chatting in Telegram and paying in sums.
Prototype and testing with real people
A clickable prototype lets you walk through the scenarios before development begins. Show it to a handful of people from your target audience and ask them to complete a task without hints. Your project team has long since got used to the product and no longer sees confusing navigation; a newcomer finds it quickly.
Also agree in advance how files are handed to developers. Mockups with specs for spacing, sizes and states save many clarification calls while screens are being built.
What drives cost and timeline
The price of app design depends on the number of unique screens, the complexity of the logic (account area, payments, chat, geolocation, filters), the number of platforms, and whether you need a dark theme or a tablet layout. A complex screen with filters costs differently from a static card, so an honest estimate is only possible once there is a brief and a screen list.
Delays usually come from approvals, not from drawing. Collect feedback in batches, name one person who makes decisions, and do not change the concept midway. That keeps the schedule predictable.
Common mistakes at the start
The first mistake is starting with a logo and palette instead of scenarios. The second is copying someone else's interface without adjusting for local habits. The third is handing mockups to developers without testing them on people. The fourth is not discussing budget up front and learning the price after the screens are drawn, which forces you to cut features.
If an app is premature, a sensible first step is a website or web version of your service, where you can test demand and scenarios. At markdev we build websites turnkey and help you judge whether you need an app right now. If you want to talk it through, send us your task and we will review the brief and suggest where to begin.
FAQ
Where do I start mobile app design if I have no technical specification?
Start with a short brief: who the user is, the key scenarios, the platform, interface languages and budget. A formal specification can be built later with your contractor from that document.
Do I need a prototype before development?
Yes. A clickable prototype tests the flow before programmers start. Changes at this stage take hours, while changes in finished code take days, so it protects your budget.
Can I design for iOS and Android at the same time?
Yes. Teams usually build one UI kit and adjust for platform differences such as gestures, navigation and system elements. That is simpler than running two separate designs.
How much does mobile app design cost?
It depends on the number of screens, the complexity of the logic and the platforms. It cannot be named without a brief and a screen list, so expect a project-based estimate rather than a price per screen.
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.