How much does a mobile app cost in Bosnia & Herzegovina?

A mobile app with me starts at 2500 KM (roughly €1,280), and that price gets you an app that runs on both iPhone and Android, because it is written once in React Native. The price goes up with the number of screens, whether you need user accounts, a database, and a connection to a system you already run. You get an exact quote free after a short call about what the app needs to do.

That is the starting price. What is more useful to know is what sits behind it — and which costs only show up once the app is finished.

What the starting price includes

At 2500 KM I build a smaller app: a handful of screens, one clear path the user follows, and data coming from a single source. Specifically, that covers:

• Screen design matched to your brand, not a bought template.
• One codebase for both systems — the iOS and Android versions are built together.
• Testing on real devices, not only in a simulator.
• Store preparation — icons, descriptions, screenshots, everything the stores ask for.
• Publishing to the App Store and Google Play under your own accounts.

The timeline is typically 8–12 weeks, and longer once the app has its own server and user accounts. It depends mostly on how quickly we settle the content and how long store review takes.

What pushes the price higher

Each of these is a project in its own right, and each one moves the price above the starting figure:

• User accounts and login. The moment people have profiles, you need registration, password resets, account deletion and a data policy.
• Your own server and database. If the app stores data, someone has to build and maintain what sits behind it.
• In-app payments. The most demanding part, technically and administratively, with rules Apple and Google enforce strictly.
• Push notifications. Simple to send, harder when they need to be smart and personalised.
• Connecting to an existing system. If you already run a till, stock or an appointment schedule, the app has to talk to it.
• Working offline. An app that must work without internet is a different project from one that does not.

None of this turns up as a surprise at the end. It is agreed in advance, in phases, with a price per phase.

Costs that do not stop at launch

This is the part business owners most often overlook. An app is not a one-off cost like printing flyers:

• Developer accounts. Apple charges a membership once a year, Google a one-off fee when the account is opened. Both accounts should be in your company's name.
• The server, if the app has one. A monthly cost that depends on how many people use the app.
• Maintenance. iOS and Android each release a new version every year. An app left untouched for two years starts breaking on its own.

The good news is that these costs are predictable, and you know them before any work starts.

Why I write one codebase for both systems

The classic approach means two separate apps — one for iPhone, one for Android — and near enough double the work. I use React Native and Expo, which means one codebase that produces both versions.

For you that means three things: a lower build cost, one fix instead of two when something needs correcting, and both versions always having the same features. There is no situation where Android users wait a month for something iPhone users already have.

What next

If you are considering an app, see exactly what I do or send me a message — describe in a couple of sentences what the app should do and who it is for. I will tell you honestly if I think you do not actually need one.

Frequently asked

Can the app be built in phases so I do not pay for everything at once? Yes, and that is usually how it goes. The first phase is an app with only what it needs to be useful. Once that works and you see how people use it, we agree the next phase.

What if a store rejects my app? It happens, most often over small things in the description, the privacy policy or a missing way to delete an account. That is part of the job — I fix it and resubmit at no extra charge.