I build apps for Android and iPhone from one codebase, on a backend shared with the browser version. I also handle the part few people warn you about: publisher accounts, the required documents, and review at Google Play and the App Store, until the app is available to download.
Two routes
The first conversation starts with choosing one of these routes, because they differ in cost, time, and what the phone can do. I advise based on how often the user is meant to come back.
When users should come back daily and keep your icon on their phone screen.
Your brand stays on the phone screen, next to the apps your client uses every day.
When a fast start and one address for every device matter most.
You launch in a few weeks and decide on a full app later.
Scope
Release
Building the app is half the road. The other half is getting through the stores' requirements, where most projects stall. I run it from account setup to an approved submission.
I set up and configure the Google Play and App Store accounts, registered to your company. The stores' registration fees are on your side: a one-off charge of about 100 zł at Google and about 400 zł per year at Apple.
Terms of service, a privacy policy, and a data-safety declaration listing every piece of information the app collects and the purpose of each. This is the most common reason submissions get rejected.
An icon, screenshots in the required sizes, a description written for the store's search, and promotional artwork. The listing is what decides whether people download.
Submission, answers to reviewers' questions, and fixes until the app is approved. I see it through, along with every release after launch.
Projects
Both are available on Google Play and both run on the same backend as their browser versions.
An education app on Google Play
A student solves exercises on the phone and picks them up on the desktop with progress intact, because both versions share one backend. Listening recordings for language practice are generated during the exercise, so the app stays lightweight.
A service app on Google Play
The client runs their website from the phone: statistics, content changes, and contact with support. The app shares its backend with the browser panel, so every new feature appears in both places at once.
Shared backend
This is how both of my apps work and how I build them for clients. It is the decision with the biggest effect on cost — at the start and through the years that follow.
The mobile app and the browser version share one database and one logic. A new feature is built once and shows up in both places.
With the backend already running, the mobile app costs a fraction of building from scratch — what remains is the interface and the release.
A fix in the business rules lands in one place, so the versions stay in step months later.
The same login, the same subscription, the same data. Users switch from phone to desktop mid-task.
Technology
One codebase covers Android and iPhone. A single app serves both systems, which shortens the build and lowers the cost of upkeep.
Tooling that puts new versions in testers' hands within minutes and delivers small fixes to users with no store wait.
Node with TypeScript and PostgreSQL on an AWS server — exactly what the browser versions run on.
Push delivery through Google and Apple services, with audience segments and open-rate measurement.
Price
An app built together with its backend starts at 30,000 zł net. With the server, data, and browser version already running, the mobile version starts at 15,000 zł, because what remains is the interface, testing, and the store release.
from 30,000 złnet, first release
What drives the price:
Store fees come on your side — about 100 zł one-off at Google Play and about 400 zł per year at Apple — plus maintenance from 800 zł per month.
Calculator
Tick what it should include. The amount recalculates as you go and shows what each item adds.
Process
Who will use the app, how often, and what they will do in it. We also check which features belong on the website.
A list of screens and user paths, split into the first release and the ones after. You approve the scope before the quote.
Screen designs for your approval, prepared separately for Android and iPhone where the systems differ.
The app grows in stages, and you get each new version on your own phone to test in practice.
Publisher accounts, documents, listing assets, and review. I see it through to approval.
New features, updates for store requirements, and responses to how people actually use the app.
After release
Google and Apple raise their requirements every year. I track the deadlines and ship updates before the store buries the app in its results.
After every major Android and iOS update I check the app and fix what changed.
Errors from users' devices reach me automatically, together with the screen they happened on.
Maintenance from 800 zł per month: backend, updates, new releases, and replies to store reviews.
Questions
An app with its own backend starts at 30,000 zł net. If the browser application and server already run, the mobile version starts at 15,000 zł, because what remains is the interface and the store release. I quote after mapping the screens.
I build in React Native, so one codebase covers both systems. For a typical business app this gives the same result as two separate apps, at a clearly lower cost of build and upkeep. Separate apps make sense for advanced graphics or very deep use of system features.
The first release usually takes three to four months, counting the visual design and store review. Later versions then ship every few weeks.
That is a normal stage and happens with first submissions. I answer the reviewers' notes, apply fixes, and resubmit until the app is approved. This time is part of the project.
Yes, and I register them to your company so the app belongs to you. The store fees are on your side: about 100 zł one-off at Google Play and about 400 zł per year at Apple.
Yes. That is the usual setup: the app uses the same backend as the website or panel, so data and accounts are shared. If your system offers an API, I connect the app to it.
Sometimes yes, and I say so on the first call. A version installed from the browser gives an icon on the screen and offline work at a fraction of the cost of a full app. An app in the store wins when you need push notifications, full access to the phone's features, and presence in the store's search.
You do. The publisher accounts are registered to your company, and the code goes to a repository you fully control, together with the copyright.
The stores raise their requirements every year and the systems get major updates. Maintenance covers tracking those deadlines, shipping new versions, reacting to crash reports, and answering user reviews.
Related services
Projects rarely stop at one thing — here is the rest of what I do, each with its starting price.
Order
A few sentences about who will use it and what they will do in it are enough. I'll reply with a proposed scope, a quote for the first release, and a schedule — usually the same day.