Do you actually need an iPhone app?
Before choosing a technology, ask why a customer would install your app when they already have Instagram, Telegram and your website. An app earns its place when people come back often: ordering delivery, booking appointments, collecting loyalty points, tracking an order, or using a personal account.
The second question is who your audience is. iPhones are very visible in Tashkent, but the picture changes in the regions and differs from one business to another. Skip generic statistics and look at the device reports in your website analytics, your ad accounts, and ask your sales team what phones customers write from. If most buyers use Android, an iOS-only app covers only part of your demand.
Native, cross-platform or web: the real options
There are several routes to an iPhone, and the most expensive one is not automatically the best.
- Native app in Swift: best performance and full access to phone features, but Android needs separate development.
- Cross-platform (Flutter, React Native): one codebase for iOS and Android, a sensible default for most business apps.
- PWA or responsive web service: opens in the browser and needs no App Store release, but has fewer capabilities.
- Telegram bot or mini app: often the fastest way to test an idea in Uzbekistan, because your customers are already in Telegram.
- A simple catalogue with ordering can launch as a web version first and become an app later.
What a project includes besides screens
First-time buyers usually count only design and programming, then are surprised by the timeline. Publishing requires an Apple developer account, which for a company is registered as a legal entity and needs verification. After that the app goes through App Store review, and small gaps can cause a rejection: no privacy policy, no demo login for the reviewer, no explanation of why the app asks for location or camera access.
Payments deserve their own check. Apple treats digital goods and subscriptions differently from physical goods and services. If you sell food, clothing or appointments, connecting Click or Payme is usually possible, but it is smarter to confirm the payment flow before development starts rather than after a rejection.
The website and backend people forget
An app rarely lives alone. It needs a server with an API, an admin panel where staff update products, prices and orders, and a public web page with a description, privacy policy, support contacts and install links. Without a website it is harder to run ads or appear in search: someone who taps a link in Instagram should land on a clear page, not a dead end.
That is why it makes sense to plan the website and the app together, with a shared product database, one customer account and the same promotions. You avoid paying twice for the same logic and maintaining two catalogues by hand.
What drives the cost
Nobody can give an honest figure without a brief, and comparing other people’s price lists is risky, because the word “app” covers very different scopes. Cost depends on the number of screens and user roles, how complex the personal account is, integrations with payments, a CRM, inventory or 1C, push notifications, support for two platforms, and whether the design is custom or template-based.
Do not forget the costs after launch: updates for new iOS versions, bug fixes, server hosting and user support. An app without maintenance ages quickly.
Choosing a team and measuring the result
Tashkent has freelancers, small studios and full-cycle agencies. The difference is not only price. Ask who is responsible after delivery, whether you receive the source code and account access, and how stages and acceptance work. The developer account and the server should be registered to your company, otherwise you become dependent on the contractor.
Agree on metrics up front: installs, the share of users who place a first order, repeat purchases and the cost of acquiring a user. That requires event analytics built into the app from day one. Without it you cannot tell whether the development pays off or the budget is simply being spent.
Where to start
A good start is a small first version with one core function that you can show to real customers. Describe the action a user must complete, collect competitor examples, choose platforms, and plan a budget for the first year, not only for development.
If you need a website that can later support an app, or you want to discuss whether an app makes sense at all, the markdev team can review your task and suggest a clear plan without inflated promises. Send us a request and we will go through your project together.
FAQ
Can I build an app for iPhone only?
Yes, if your audience mostly uses iPhones or you are testing an idea on a limited group of customers. In many cases cross-platform development is more efficient because it covers both iOS and Android.
Do I need an app if I already have a website and a Telegram bot?
Not always. If customers rarely return and ordering through the site or bot is enough, an app may not pay off. It makes sense when personal accounts, bonuses, notifications and regular use matter.
Why might the App Store reject an app?
Common reasons include a missing privacy policy, a demo login that does not work, breaking the rules for digital goods payments, too little functionality, or an app that simply repeats the website. It is better to plan for these before development.
Who should own the Apple developer account?
Your company. That way the app, the source code and the access credentials stay with you even if you change contractors.
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.