Mobile apps that make it through the stores
The most expensive mistake in a mobile app is not in the code — it is in the scope. We start with a version you can ship and measure, then build out only what people actually use. We publish our own apps, so we also know the part nobody talks about: App Store and Google Play review.
net, per project — a realistic MVP scope with backend and store publishing
What we do
From a single-platform MVP to a product with an admin panel, payments and client-side integrations. We pick the technology for the budget and the product’s lifespan, not for fashion.
What an app actually includes
The things clients usually discover mid-project — with us they are costed from the start.
How we run it
Four stages — from scope to an app live in both stores.
How we know this
We publish our own apps and go through store review ourselves — rejections included.
Frequently asked questions
Cost, time, and what happens after launch.
How much does a mobile app cost?
Mobile apps start at 8,100 PLN net with us. That is a realistic MVP scope: one platform or a shared codebase for iOS and Android, a handful of screens, a backend and store publishing. A larger product with payments, offline mode, an admin panel and integrations is usually 30,000–120,000 PLN. The biggest price drivers are the number of screens and whether the app has to talk to your systems.
How long does an app take?
An MVP is typically 8–12 weeks from kickoff to publication; a larger product runs 4–6 months. On top of that comes store review: Apple usually takes 1–3 days, but a first submission often comes back with notes, adding another cycle. We build that margin in upfront so the launch date is realistic.
Native or one codebase for both platforms?
A shared codebase makes sense for most business apps — you get both platforms for close to the budget of one, and users will not notice the difference. We go native when the product leans on hardware, needs maximum smoothness with large lists, or integrates deeply with the OS. We recommend after discussing the features, not upfront.
Do I need a separate backend?
Almost always. The app is the interface; data, accounts, notifications and the admin panel have to live somewhere. Our quote includes the backend from the start — that is a common reason competing offers look cheaper and end in a surcharge.
Who handles App Store and Google Play publishing?
We do. We set up or configure developer accounts under your company, prepare descriptions, screenshots, privacy policy and data declarations, then run the submission through to approval. The accounts stay yours — which matters if you ever change supplier.
What if Apple rejects the app?
That is a normal part of the process, not a failure. The most common reasons are missing account deletion, an unclear subscription description, or a feature the reviewer cannot reach. Fixes after a rejection and resubmission are included in the project price — we do not bill them separately.
What does upkeep cost after launch?
The app does not break on its own, but the systems around it change: new iOS and Android versions ship every year and the stores raise their requirements. Budget for a few technical updates a year. We can run that on a retainer or hourly — your choice.
Do I get the code and the accounts?
Yes. Once the project is settled we transfer full economic rights to the code, the repository, backend access and the App Store Connect and Google Play Console accounts. Nothing stays on our side.
Mobile apps
Let us price your app
A free 45 minutes on features and audience, then a prototype of the key screens and a fixed price.



