Services & Catalog
from 4 500 000 UZS
Catalog of services and products, request or booking, contacts — for businesses and service centres.
Order now Mobile App Development
Mobile App Development — Android and iOS Apps
Catalog and services, store and delivery, startup system — Android and iOS apps from a single Flutter / React Native codebase. Price from 4 500 000 UZS, we publish to the App Store and Google Play for you.
- Starting price
- 4 500 000 UZS
- Timeline
- from 3 weeks (catalog) to 6 weeks (store, delivery)
- Languages
- Uzbek, Russian, English, Tajik
- Code
- Fully handed over to you
A mobile app means a permanent place on your customer's phone: push notifications, quick ordering, a personal account, map and payment on one screen. We work with Flutter and React Native — one codebase, both platforms, simultaneous updates; far cheaper and faster than writing two separate apps.
Backend server and REST API, admin panel, SMS/phone login, Payme/Click payments, map and geolocation, push notifications — all in one order. We also handle developer account setup, review and publishing to the stores.
Types and prices
A type surcharge is added to the base price — the numbers in the table are "starting from" prices.
E-Commerce & Delivery
from 5 500 000 UZS
Online store and delivery: cart, payment, order status, courier and map.
Order now Learn moreCustom Startup Solution
from 6 550 000 UZS
Custom startup system: unique business logic, roles, real-time features, integrations.
Order now Learn moreTarget Platforms
- Android Only Included in base
- iOS Only +650 000 UZS
- Android + iOS +1 900 000 UZS
Features
Pick what your project needs — each feature is added to the price separately.
- Backend Server & API +1 800 000 UZS Database and high-performance server logic Learn more
- SMS & Phone Auth +650 000 UZS Fast and secure login via phone number
- Push Notifications +500 000 UZS Alerts and promo notifications
- In-app Payment +1 150 000 UZS In-app checkout with credit cards
- Maps & Geolocation +900 000 UZS Interactive map location picker
- App Store & Google Play +750 000 UZS Store assets and review approval support Learn more
Prices are in UZS, excluding VAT. The final amount depends on the options you choose and is shown before you place the order.
Technologies
A fast, secure stack with long-term support — the project outlives any change of developer.
- Flutter
- React Native
- Laravel REST API
- PostgreSQL
- Firebase Push
- Payme, Click
- Google Maps / Yandex Maps
- App Store, Google Play
Apps we build
- Android app development
- iOS app development
- Delivery app
- Online store app
- Service catalog app
- MVP for startups
- Taxi and courier apps
- Booking and queue app
- Software development
- Hire mobile app developers
Additional services
Services you can add to any order — hosting and domain, server, app store accounts, training and technical support.
- 1 Month Technical Support +400 000 UZS Free bug fixes and consultation
- 3 Months Technical Support +900 000 UZS Free bug fixes and consultation
- Production Server Setup & SSL +500 000 UZS Complete deployment and configuration on your own server
- Video Training Guide for Team +400 000 UZS Step-by-step video tutorials on managing the system and dashboard
- Apple & Google Developer Accounts Setup +850 000 UZS Full corporate developer account registration and verification
Prices are in UZS, excluding VAT. The final amount depends on the options you choose and is shown before you place the order.
What you receive
A mobile app is the largest of the three services and the one with the most moving parts, so it is worth being precise about what actually arrives at the end. This is what the base price covers, before any option is added to the order.
-
The screens, drawn first
The whole path through the app is agreed as a mockup before development starts: what opens first, what each tap leads to, what an empty list looks like. Changing a screen on paper takes an hour. Changing the same screen once the app is built takes days.
-
Android and iOS from one codebase
The app is written once in Flutter or React Native and built for both platforms, so a change made today appears in both stores in the same release. It costs far less than two separate native apps and stops the two versions drifting apart from each other over time.
-
Builds you can install
You receive the installable packages for both platforms along with the signing files and configuration needed to publish them and to publish updates later. Those files matter more than they look: without them a future update cannot go to the same listing, whoever ends up building it.
-
The source code, in full
The repository, the dependency list and step-by-step build instructions are handed over, so the app can be compiled by anyone competent without contacting us first. The project is not tied to our machines, our accounts or our continued involvement, and nothing is withheld as leverage.
-
Tested on real devices
The app is tried on real phones with different screen sizes and different operating system versions, not only in a simulator. A simulator will not show you a slow device, a cramped screen, a weak network, or the way an older Android version handles permissions and background work.
-
Connected to its data
The app talks to the API it was designed against, with the data models, error handling and offline behaviour that implies. If you chose the backend option, that API and the side you administer it from are built as part of the same project rather than assumed to exist.
What you supply
An app estimate is only as good as the description it was made from, which is why the first item below matters more than all the others put together. These are the things needed from your side before development starts and before the app can be published to a store.
-
What the app does, screen by screen
Write out what a user can do, screen by screen: register, browse, search, order, pay, look at history. Vague descriptions produce vague estimates and arguments at delivery. A precise list is what makes a fixed price and a fixed deadline possible in the first place.
-
Brand assets
The logo in its original file, your colours, and an icon. The icon deserves real attention, because it is what a store shows next to your name and what sits on a home screen among dozens of others. A small, blurry or crowded icon quietly costs you installs.
-
A backend, or the decision to build one
An app whose content changes needs somewhere for that content to live. Either you already have a system with an API the app can connect to, or the backend API option is added to the order and it is built alongside the app. There is no third possibility.
-
Store accounts
Publishing needs an Apple developer account and a Google Play developer account. Use your own, or choose the option that has them opened in your company's name. Verification takes time and Apple in particular can be slow, so start this well before the app itself is finished.
-
The content
The products, categories, descriptions, prices and images the first version launches with. An app reviewed by a store with an empty catalogue looks unfinished and can be rejected for exactly that, so the first batch of real content has to be ready before the app is submitted.
-
Someone to test it
One person on your side who installs every build, uses it properly and writes down what is wrong. Review cycles stall without that person, and a build that waits a week for feedback pushes the whole schedule by a week, however quickly the fixes themselves are made.
After handover
A published app lives in somebody else's house: two stores with their own rules, and two operating systems that change every year. This is what belongs to you once the work is handed over, and what will need attention across the life of the app, whoever does it.
-
The accounts and the code are yours
The app is published under your own developer accounts, so both listings, the reviews, the ratings and the download statistics belong to you. Together with the source code that means the app can be maintained by anyone you choose afterwards, including your own developer later on.
-
Store review
Both stores review every submission and either of them can reject one, sometimes over something small such as a missing privacy policy or a permission that is not explained. Correcting a rejection and resubmitting is part of getting the app published, not an extra charge afterwards.
-
Operating systems move
Android and iOS release a new version every year and periodically raise the minimum requirements a published app has to meet. An app nobody touches for a couple of years eventually needs rebuilding to stay in the stores, and that is the kind of work the support package exists for.
-
Push notifications
If you chose the push option it is configured and tested, and you send the messages yourself afterwards. Treat them carefully. Notifications that are genuinely useful keep an app installed, and notifications sent for the sake of activity are the fastest way to be uninstalled and forgotten.
-
Bugs are fixed free
Anything that does not work the way it was agreed is corrected at no charge after handover, including a fix that has to go back through store review before your users can get it. New screens and new features are a new order rather than a bug report.
-
The next version
New features arrive either through a support package or as a separate order, and the code is structured so that adding them does not mean starting again from nothing. It is normal for the second version to be shaped by what real people actually did with the first.
Common mistakes
An app is the most expensive of the three services, which makes a mistake at the ordering stage the most expensive mistake as well. These are the ones that come up again and again, and every one of them is a decision rather than a technical fault.
-
An app before a website
People find a website. They install an app deliberately, and usually only because they already deal with you. If nobody is searching for your business yet, a site will earn more than an app for the same money. An app is for the customers you already have.
-
Store rules
Both stores reject apps that are only a website in a wrapper, that ask for permissions they clearly do not need, or that ship without a privacy policy and a way to delete an account. Read those rules before designing around something that will not be allowed through.
-
No backend, no data
If prices, products or texts have to change after release, they cannot be written into the app itself: every change would mean a new build and another round of store review. Content that moves needs a backend, and deciding that late means rebuilding the parts that assumed otherwise.
-
Store accounts have a yearly cost
The Apple and Google developer accounts are yours and are renewed by you. Let one lapse and your app disappears from that store until it is paid again, which is an avoidable way to lose a listing you spent weeks getting through review in the first place.
-
Everything in version one
The instinct to put every idea into the first release is what makes an app expensive and late. The first version should do one thing properly. Everything else is easier, cheaper and better aimed once real people are using it and telling you what is missing.
-
Testing on one phone
A build that works on your phone proves that it works on your phone. It has to be tried on a small screen, on an older operating system version and on a slow connection as well, because that is what a large part of your users will actually be holding.
Landing or corporate? Bot or app?
This is where most buyers stop before ordering. Put the two side by side — criteria, timeline and the price each starts at.
How we work
From order to delivery — five steps, and you stay in control at every one.
- 1
Order and price
Choose the service and features on the site — the price appears instantly. The team contacts you via Telegram or phone.
- 2
Technical spec
Goal, audience, list of pages/features and timeline are confirmed in a short document.
- 3
Design
We show a mock-up that matches your brand; once revisions are approved, development begins.
- 4
Development and testing
You follow progress on a live link. We test on mobile, for speed and for security.
- 5
Delivery and support
Server deployment, hand-over of code and credentials, training your team. Then — technical support.
Frequently asked questions
Frequently asked questions
The most common questions about price, timeline and process.
How much does mobile app development cost?
A catalog/service app for one platform (Android) starts from 4 500 000 UZS. Android + iOS, sales and delivery or a custom startup system increase the price — the most complex configuration from 6 550 000 UZS. Backend API, SMS login, push, payments, maps and store publishing are chosen separately.
Do you build Android and iOS separately?
No — with Flutter or React Native one codebase produces apps for both platforms. That is half the cost, and updates ship simultaneously.
Does the app need a server (backend)?
If the app works with user data, orders or a catalog — yes. The "Backend server & API" feature includes an admin panel and REST API on Laravel; if you already have a system, we connect to it.
Who publishes to the App Store and Google Play?
We do. The "Google Play & App Store" feature covers preparing the app, passing review and publishing; developer account setup is ordered separately as an additional service.
How long does the app take?
Catalog/service app — 3–4 weeks, sales and delivery — 4–6 weeks, startup system — per the technical spec. Once the design is approved, the timeline is confirmed in writing.
How is the work paid for?
Payment is staged: an advance to start, the remainder when the app is delivered. The amount comes from the options you tick in the order form and is visible before you pay; anything added later during the build is agreed separately.
What is handed over once the app is finished?
The full source code of the app and of the backend, admin panel access, and the signing keys and account settings used for publishing. From there you can ship updates yourself or hand the project to another team.
Why can App Store or Google Play review take longer?
Review runs by the stores' own rules. The usual causes of delay are a missing privacy policy, no test account for the reviewer, a description that does not match what the app actually does, or paperwork on the developer account. If the app is rejected, we fix the point raised and resubmit.
What running costs appear after release?
Google Play and App Store developer accounts have their own fees, and those are paid directly to the stores. If a backend was ordered, server costs are added. Bug fixes stay free, while new features and monitoring go through a 1- or 3-month support package.
What features can the app have and what do they cost?
Backend API +1 800 000 UZS, SMS login +650 000 UZS, push notifications +500 000 UZS, in-app payment +1 150 000 UZS, maps and geolocation +900 000 UZS, publishing to the stores +750 000 UZS. Each option is chosen separately in the order form.
Calculate the price now
Tick the features, see the final amount and place your order — the team gets back to you within one business day.