Mobile app development for iOS and Android
We build apps people open a second time. From the first sketch to App Store and Google Play, with one codebase for both platforms when that makes sense — and native code when it does not.
A mobile app is not a website in a phone
The difference is context, not screen size. People open apps in a lift, on the street, one-handed, on a bad connection, at 12% battery. If your app needs three screens to do the thing it was installed for, it gets deleted in the first week.
So we start with one question: what is the action this user will repeat a hundred times? That becomes the main screen, and everything else arranges itself around it. It is a product decision, not a design one, and it happens before the first line of code.
Cross-platform or native: how we choose
For most business apps — orders, bookings, reporting, internal workflows — we use React Native. One codebase for iOS and Android halves development time and, more importantly, leaves one codebase to maintain through every OS release.
We go native, with Swift or Kotlin, when the app depends on something the cross-platform bridge cannot do well: real-time video processing, Bluetooth with medical or industrial devices, high-frequency sensors, maps drawing thousands of points at once.
We tell you which category you are in up front. If you do not need native, we will not sell you native — it costs twice as much and you maintain it forever.
The part nobody shows you in a demo
Publishing. Apple rejects a share of submissions on the first attempt, and the reasons are rarely technical: a missing privacy policy, no account deletion, a description promising something the app does not do.
We handle the developer accounts, the store listings, the screenshots, the privacy policy and the replies to rejections. It is not the interesting work, but it decides whether the app reaches people or stays on our laptops.
- Apple Developer and Google Play Console accounts, opened in your company's name
- Complete store listings: description, screenshots, keywords, category
- Signing, certificates and provisioning profiles, documented
- Updates shipped without going through us every time
What happens after launch
This is where most apps die. iOS ships a new version every September, Android every August, and an app left untouched for a year starts breaking in ways you only see in one-star reviews.
The monthly retainer covers exactly that: the app stays compatible with new systems, libraries get updated, and errors reach us automatically rather than through complaints.
What you get
- App in both storesPublished under your developer account, meeting each store's review requirements.
- Admin panelWeb-based, so you manage users, content and orders without calling us.
- API and databaseThe backend, hosted and monitored, with daily backups.
- Source code, yoursIn your repository from day one. You can leave with it whenever.
- Crash reportingUser crashes reach us automatically, with the screen and steps that caused them.
- RunbookHow to ship a new version, where the keys live, what to do when something breaks.
What we build it with
- React Native
- Expo
- TypeScript
- Swift
- Kotlin
- Java
- Spring Boot
- Node.js
- PostgreSQL
- Push notifications
- Authentication
- Payments
- Maps
What a mobile app costs
from €599
A first package covers an app with one main flow done properly, published to both stores, with an admin panel. Apps with payments, maps, real-time messaging or integrations with existing systems fall into the later packages. You get a firm price after a 30-minute conversation, not an estimate that doubles along the way.
Frequently asked questions
How long does mobile app development take?
Between 2 and 6 months depending on complexity. An app with one main flow and an admin panel reaches production in around two months. One with payments, real-time messaging and integrations approaches six.
Will the app work on both iPhone and Android?
Yes. We use React Native for most projects, which means one codebase for both. Building for a single platform is not much cheaper, so it is rarely worth limiting yourself.
Who owns the code and the store accounts?
You do. The code sits in your repository from day one, and the Apple Developer and Google Play accounts are opened in your company's name. If you want to work with someone else tomorrow, there is nothing to recover from us.
What if Apple rejects the app?
We handle the response and the fixes at no extra cost. Most rejections are policy, not code, and we design around them from the start.
Do I need a monthly retainer after launch?
You need someone keeping the app compatible with new iOS and Android releases, or it degrades within a year. Our retainer covers that, plus hosting and monitoring. You can stop any time; the code stays yours.
Tell us what you want to build
Three steps, a few minutes. You get a code to follow your request and the project's progress in real time.