What drives the price
An app’s price is set by what happens between screens, not by how many there are. MVP covers the key flow, one user role, push notifications, analytics and release in both stores: enough to test the product on real customers. Standard adds a customer account, payments, in-app support chat and an admin panel, which is what most service apps look like. Advanced brings real-time features, maps and courier tracking, offline mode and a separate staff app, the other side of your service. Face ID, loyalty cards, widgets, stories and AI features are add-ons. The configurator builds the total, and it goes into the contract with the deadline.
How the work runs, week by week
We start with discovery: why a customer would use an app rather than a website, and which actions they will repeat most. That gives us flows and a screen map, then a clickable prototype you open on your phone. Development runs in two-week cycles; at the end of each you install a test build on your iPhone or Android and see what is done. In parallel we prepare developer accounts, store listings and screenshots. The final stretch is testing on real devices, including budget Android phones, Apple and Google review, and the first release. The timeline from 10 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract in total.
Payments, stores and languages
Store rules decide how money flows. Physical goods and services can be paid through local providers; in Uzbekistan that means Payme and Click inside the app. Digital content and subscriptions must go through Apple’s and Google’s in-app purchases, so we build that into the revenue model early, before it can hold up review. Publishing as a company on the App Store requires your company’s D-U-N-S number, which takes time to obtain, so we request it in the first weeks. Interfaces are multilingual, with layouts designed for longer strings: a button that fits in English may not fit in German or Uzbek. We test on budget phones and slow networks.
When you do not need an app, and where projects fail
If customers come once a month, an app will not pay off: a Telegram Mini App or a website that installs to the home screen (PWA) will do, and we will say so before any contract. When an app is right, projects fail in the same places. An AI-generated prototype with no engineering review often keeps API keys inside the app, where anyone can extract them. The server does not check permissions, so one user sees another’s orders. Payments are never reconciled with the provider. There is no crash monitoring, so failures surface in store reviews. Bugs are fixed free with no time limit, and your engineer may audit the code against the contract: any unfulfilled item means a 10% refund.