Published: · 4 min read
A question about app pricing often ends with one number that is either far too low (and then doubles) or far too high (and the project never starts). This article breaks the budget into parts — so you know what you pay for, what can be postponed and where the costs hide that proposals rarely mention.
The starting price and what it means
At webandapp mobile app development starts at GEL 1,100 — the cost of a simple first release (MVP): a few screens, one core function, basic design, one code base for Android and iOS. Everything added on top — login and roles, a backend, payments, notifications, integrations — raises the price in stages. That is why an app budget is calculated from a feature list, not from a single “app” price.
What creates the cost
- Number and complexity of screens. A list, a detail page and a form are one cost; a real-time map, chat or drag-and-drop calendar are another.
- Backend. If the app stores users, orders or messages, it needs a server, database and API — often half the budget, plus ongoing hosting.
- Authentication and roles. Guest mode is simple; phone/email registration, social login and different admin/user permissions are additional work.
- Payments. Bank or provider integration, or in-app purchases through the stores with their commission for digital goods.
- Device features. Camera, GPS, push notifications, biometrics, offline mode — each needs platform-specific configuration.
- Integrations. CRM, accounting, warehouse, an existing website — data exchange needs work on both sides.
- Design. Standard components or a custom interface with animations.
- Admin panel. Managing users, content and orders usually needs a separate web panel that clients forget about.
MVP or full version
An MVP solves only the core task. Its advantage is less about price than risk: before investing in a full product you test with real users whether they need it at all and which functions are actually used. In practice the second version’s feature list almost always differs from the initial assumption — and an MVP reveals that difference before the budget is spent. Simple rule: if the app is still useful without a function, it does not belong in the MVP.
iOS and Android: together or separately
Two separate native apps (Swift and Kotlin) mean two code bases, double testing and double updates. React Native or Flutter build both platforms from one code base — usually a little more than one native app and noticeably less than two. Native development makes sense when an app relies on one platform’s specific capabilities or needs extreme performance. With a limited budget, starting with one platform — where most of your audience is — is also logical.
Costs proposals rarely mention
- Developer accounts. The Apple Developer Program is an annual fee (USD 99 per year at the time of writing); Google Play Console is a one-off registration fee (USD 25). Current rates are on the platforms’ sites; both accounts are opened in the business’s name.
- Server and database. A monthly cost that grows with the number of users.
- External services. SMS verification, maps, push notification services, email sending — by usage.
- Store commission. For in-app purchases of digital goods the platforms keep a percentage.
- Updates. iOS and Android change every year; an app needs a technical update at least annually to stay in the stores.
- Test devices. Android’s variety requires checks on several real devices.
Planning the budget in stages
- Stage 0 — prototype (Figma). Screens and transitions without code. Cheap, shows the idea and often changes the feature list before development.
- Stage 1 — MVP. One core function, a basic backend, one code base for both platforms, publication.
- Stage 2 — by feedback. The functions real users ask for — not the ones assumed at the start.
- Stage 3 — scale. Integrations, automation, extended administration, performance.
This split gives two things: each stage has a concrete price, and you can stop at any stage if the market says otherwise.
You may not need an app at all
Many tasks people request an app for are solved by a mobile-ready website — cheaper and without store reviews. An app is justified when users open it regularly, need notifications, offline mode or device features, or when it is a tool for staff. If unsure, describe the task — that is often exactly what we work out at the first meeting. Full service description: mobile app development; starting prices: pricing page.