Mobile app development for Android and iOS, from idea to release on Google Play and the App Store. Before a single line of code is written, one decision drives both cost and timeline: whether you need a native app, cross-platform, or whether a PWA is enough. A simpler app reaches release in 6 to 10 weeks.
This is the decision that most affects the budget. There is no universally right answer - only the one that fits your case.
A separate app for Android and another for iOS. Best performance and full hardware access - camera, sensors, Bluetooth, background work. The most expensive option because the work is done twice. Makes sense for games, image processing or heavy hardware use.
One codebase shipping to both platforms. Noticeably cheaper and faster than native, and the speed difference is imperceptible for most business apps. This is the choice on the majority of projects we run.
Runs in the browser but is added to the home screen and behaves like an app. No store release, no waiting for approval, and it updates instantly. Limited on iOS notifications and hardware access.
A fair question rarely put to a client: you may not need an app at all. Check this before investing:
If most answers are no, we will tell you honestly that a good website is the better investment. We would rather lose a project than build an app nobody uses.
Field staff enter data, scan barcodes, take photos and capture signatures. Works without internet and syncs when the connection returns. The most common request from companies doing delivery, service and stocktaking.
Clients pick a slot, get a push reminder and can cancel without a call. For salons, clinics, workshops and gyms.
Catalogue, cart, payment and order tracking. Worth it for repeat purchases - for one-off buying an online store performs better.
Time tracking, travel orders, leave requests, internal communication. Replaces paper forms and Viber groups.
Sign-in, profile, content by access level and subscriptions. For clubs, schools and content platforms.
If you already run software or an ERP, the app connects to it through an API and serves as mobile access - without rebuilding everything from scratch.
We list what the app must do and, just as importantly, what it will not do in version one. The largest cause of missed deadlines is scope that grows along the way.
Before development you get a prototype you can tap through on a phone. That is where things get fixed which would otherwise cost ten times more later.
We build the app and the backend feeding it data. We work in short cycles, so every couple of weeks you get a build to test on your own phone.
Testing on real devices, preparing store assets for Google Play and the App Store, and going through their review. Release can take several days, and longer with Apple.
Release is not the end of the project but the start of a second phase, and it is the part that most surprises clients building an app for the first time.
The stores require maintenance. Google and Apple raise the minimum system version and introduce new rules every year. An app that is not updated eventually gets removed from the store.
The accounts are yours. Google Play and App Store accounts must be registered to your company, not the agency. This is the one point we do not compromise on - we have seen too many companies lose access to their own app.
Installs do not happen by themselves. An app in the store is not a marketing channel. People have to be brought to it - through existing clients, your website, ads or direct communication.
Version one is not final. Only once people start using it do you see what is really needed. That is why we keep version one small and leave room to build on.
Price is not calculated per hour but by scope. Five things move the figure:
After the first call you get a written quote with a fixed price, a timeline and a clearly stated scope for version one.
A simpler cross-platform app reaches release in 6 to 10 weeks. An app with its own backend, user accounts and integrations takes 3 to 6 months. Native development for both platforms takes longest because the work is done twice.
In Bosnia Android is considerably more widespread, so many companies start with it alone and halve the initial cost. If you go cross-platform, both versions come from the same codebase so there is no reason to choose.
A website is almost always cheaper. An app pays off when the same people use it repeatedly or when you need the phone hardware - camera, GPS, offline work, push notifications. Otherwise we recommend a site.
You do. The source code and the Google Play and App Store accounts are in your company’s name. If you continue with someone else tomorrow, we hand everything over without conditions and without charging for the handover.
A PWA is a web app added to the home screen that behaves like a real app. No store release and it updates instantly. It is enough when you do not need serious hardware access - and it is considerably cheaper and faster to build.
Maintenance is a monthly line and depends on complexity. It covers updates for new Android and iOS versions, error monitoring and small changes. An app that is not maintained eventually gets removed from the store.
We can, provided we get the source code and the accounts. We review the code first and tell you honestly whether it is worth continuing on the existing base or cheaper to start over.
It can, if designed that way. Offline work with syncing is a standard requirement for field apps and adds development, but is feasible on every approach except parts of the PWA scenario.
Describe it in a couple of sentences and we will tell you honestly what is feasible, in what timeframe, and whether you need it at all.
Book a call
