What a mobile app MVP is, and what it is not
MVP stands for minimum viable product: one core scenario that works from start to finish. For a food delivery service in Tashkent that might be "pick a dish, place the order, pay with Click or Payme". A loyalty programme, courier chat and a dozen filters can wait. The point is to watch real behaviour instead of collecting opinions from friends.
An MVP is not a Figma mock-up or a rough draft you plan to fix later. It has to be a live product, modest but stable. If even the narrow scenario keeps crashing, you end up testing your users' patience rather than real demand.
Do you need an app at all, or is a website or Telegram bot enough
Many customers in Uzbekistan spend much of their day in Telegram and Instagram, and are used to ordering through chats. For a first test, a cheaper channel often does the job: a responsive website, a Telegram bot, or a mini app inside Telegram. Nobody has to download anything, and you see sooner how many people actually reach payment.
A native app earns its place when push notifications are your main channel, when you need the camera, geolocation or offline mode, or when customers return often: taxis, fitness, education, loyalty schemes. If people use the service once or twice a year, an app is usually overkill.
A sensible order is a website with a clear offer and a request form, then a bot, then an app once demand is confirmed. You need the website anyway, because ads and search traffic will land there.
What goes into the first version
The test for every feature is simple: without it, can the user still get the main value? If yes, it goes on the "later" list.
Plan the interface in both Uzbek and Russian from day one. This is not decoration. If a person cannot understand your product, the rest of the features do not matter.
- Phone number login with an SMS code, no long forms
- One main scenario from entry to result: an order, a booking or a purchase
- Familiar payment options: Click, Payme or cash on delivery
- A simple admin panel where you see requests and edit content yourself
- Order status notifications by SMS or push
- Basic event analytics: sign-up, add to cart, payment
What drives the cost of an MVP
The price depends on the scope of work, not on the word "MVP": scenario design and analysis, interface design, platform choice (iOS, Android or both; a cross-platform approach avoids building two separate apps), the server side and admin panel, integrations with payment systems and an SMS provider, publishing to the App Store and Google Play, and support after launch.
Every extra screen and every integration adds work. Ask a contractor for an estimate broken down by stage rather than a single total. That way you can see exactly what to cut or postpone.
How to test demand and which numbers to track
Some assumptions can be checked before you reach the app stores. Build a waiting list on a landing page, send Meta Ads traffic to it and count how many people leave their contact details. It is an inexpensive test before any serious spending.
After launch, agree on metrics in advance: how many users reach the first target action, how many come back the following week, and what it costs to acquire one user. Without analytics you cannot tell "people dislike the product" from "people simply never found the app".
The result leaves you three options: keep developing, change the scenario, or stop. Stopping after an MVP is still a result, because you have kept the budget of a full build.
Common mistakes at launch
Most problems come from management decisions rather than technology. The last item below deserves special attention: if access to the developer accounts and the source code is not written into the contract, changing teams later becomes hard.
- Trying to copy the full feature set of large services such as Uzum straight away
- Not defining who the target user is and where they spend their time
- Launching without analytics and having no idea what happens inside the app
- Forgetting promotion: an app will not find its audience in the store on its own
- Choosing a contractor on the lowest price alone and leaving code and account ownership undefined
Where to start
Write your hypothesis in one sentence, describe a single scenario and pick the cheapest way to test it. The markdev team helps with exactly this path, from a turnkey website with analytics and request forms to an honest assessment of whether you need an app right now. If you would like to discuss your project, leave a request and we will review the idea and suggest the minimum scope for a first version.
FAQ
How is an MVP different from a prototype?
A prototype shows how the product will look and is used for discussion. An MVP is a working version that real people use, so you can measure demand and behaviour with it.
Can I start without a mobile app?
Yes. To test an idea, a website, a Telegram bot or a Telegram mini app is often enough. They are cheaper to launch and need no installation. An app makes sense once demand is confirmed.
How much does a mobile app MVP cost?
No honest figure is possible without a defined task. The cost depends on the number of screens, platforms, payment and SMS integrations, the server side and support. Ask for an estimate by stage.
What should I do after launching an MVP?
Look at the metrics you agreed in advance: completion of the main scenario, returning users, acquisition cost. They tell you whether to develop the product, change the scenario or stop.
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.