First, check whether you need an app at all
An app means a store download, space on the phone and a steady reason to open it. For a delivery service, a clinic chain, a gym with bookings or a shop with repeat orders, that usually pays off. If customers contact you twice a year, they will likely delete the app within days.
Ask one blunt question: what will a customer do in the app more than once a month, and why is that awkward on your website or in Telegram? A clear answer means you can move on to choosing an approach.
Three routes: two native apps, cross-platform, or one platform first
Native development means a separate iPhone app in Swift and a separate Android app in Kotlin. Two codebases, often two teams. You get full access to system features and the most natural behaviour, but build, testing and long-term maintenance effort nearly doubles.
Cross-platform development with Flutter or React Native uses one codebase to produce both versions. For a typical business app with a catalogue, cart, account area, bookings and order history, this is normally enough. Limits show up with heavy graphics, Bluetooth hardware or deep system integration, where native modules get added.
The third route is launching on one platform and adding the other later. It makes testing an idea cheaper, but customers on the other platform have nothing to install on day one, and they tend to say so in reviews and Instagram comments.
- Catalogue, orders, account area, tight budget: usually cross-platform
- Advanced camera, AR, heavy graphics, hardware work: native or a hybrid
- Need to validate demand quickly: cross-platform or a single platform
How Android and iOS differ for a project
The difference goes beyond programming languages. It affects timelines, testing and what happens after release.
- Design: Apple and Google have their own habits for navigation, the back action and system dialogs. Your brand styling can match across both, but core behaviour should feel familiar.
- Devices: iPhones come in a limited range. Android has many makers, screen sizes and system versions, so testing must cover more devices, including cheaper and older ones.
- Background work: some Android manufacturers aggressively limit background processes to save battery, so push notifications and location can behave unevenly.
- Publishing: each store needs a developer account, review rules differ, and approval time varies, so plan for it. Open the accounts in your company's name, not your contractor's.
- Payments: stores require their own billing, with a commission, for digital goods and subscriptions, while physical goods and real-world services can usually use outside payment providers. Rules change, so check current terms.
Which platform matters more for your audience
Ignore generic market claims and open your website analytics. Look at the share of Android and iPhone visitors in your own niche. A premium service in Tashkent can have a very different mix from an affordable shop serving the regions.
Android is widely used in Uzbekistan, but that does not make iOS safe to skip: higher-spending customers often carry iPhones. When your data is thin, cross-platform lets you avoid betting on one side.
What the budget is made of
No honest figure exists before the scope is clear, but the components are known: interface design, the client app, the server side with an admin panel, integrations (Click or Payme payments, SMS, CRM, accounting), testing on real devices and store publishing.
The backend is shared whatever approach you pick. Both apps talk to one API and database, so prices, promotions and order statuses match for everyone. Do not forget upkeep: new iOS and Android versions arrive every year, and an app that is not updated starts to misbehave or gets blocked from new store releases.
When a Telegram bot beats an app
Many customers in Uzbekistan already spend their day in Telegram. A bot needs no download, takes orders, bookings and payments, sends notifications and connects to your CRM. Often it solves the same problem faster, and a full app follows once demand is proven.
If you are unsure which format fits, the markdev team can help you work through the task: we compare an app, a bot and a website against your audience and budget. Describe what your customer needs to do, and we will suggest a sensible first step.
FAQ
Should a business choose native or cross-platform?
For catalogues, orders, bookings and account areas, cross-platform is usually enough, with one team and one codebase to build and maintain. Native fits advanced graphics, AR or deep hardware integration.
Can I launch on Android only at first?
Yes, if your analytics show most of your audience uses Android. But iPhone users get nothing on launch day, so many businesses choose cross-platform from the start.
Does the app need updates after launch?
Yes. New iOS and Android versions arrive, and store and payment requirements change. Budget for maintenance, not just the initial build.
Can a Telegram bot replace an app?
A bot takes orders, bookings and payments inside the messenger, needs no installation and connects to a CRM. For testing demand, it is often faster and cheaper than building two apps.
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.