An app that ships on schedule
React Native, with native modules where they genuinely earn their place. One codebase, two stores, and a release process that does not turn every update into an event.
Where mobile projects usually fall apart
Rarely on the code. Most often on scope, the release process, and what happens after launch.
- 01
Scope grows faster than the team
Version one was meant to have login and an order list; three months later it also needs chat, a loyalty scheme and a payments module. The deadline stops existing.
- 02
Store submission is a surprise
Developer accounts created in launch week, certificates on an employee's personal Apple ID, rejection over a privacy policy. Each of those costs a week.
- 03
Nobody owns it after launch
An app with no maintenance plan stops working properly at the next major OS release. Stores force SDK updates regularly and that is not optional.
What we do
From wireframes through to caring for the production release.
Workshop and version-one scope
We agree what has to be in version one and what waits. Version one exists to reach the store, not to contain everything — that is the only way a deadline survives.
Mobile interface design
Aligned with both platforms' guidelines, accounting for gestures, offline states and accessibility. A clickable prototype before the first line of code.
React Native build
A shared codebase with native modules where performance or hardware access demands it. Typed code and tests on the critical paths.
Push, payments, offline mode
Segmented notifications, in-app purchases and external payments compliant with store policy, and offline operation that syncs once connectivity returns.
CI/CD and OTA releases
Automated builds and test distribution, plus over-the-air fixes without a store review round where the rules permit it.
Submission and care
Developer accounts under your company, store assets, privacy policy, data declarations and shepherding through review. Then crash monitoring and regular updates.
How we run it
- 01
Weeks 1–2 — workshop
Agreeing version-one scope, user journeys and technical requirements. Output: a prioritised feature list and a quote.
- 02
Weeks 2–5 — design
Wireframes, clickable prototype, testing with a handful of users. Changes in a prototype cost hours; in code they cost days.
- 03
Weeks 5–13 — build
Two-week sprints with builds on TestFlight and the Google Play internal track after each one.
- 04
Weeks 13–16 — release
Device testing, store assets, review and launch. Slack for a rejection and fixes is built into the schedule.
What it costs
quoted after the workshop
A straightforward utility app starts around €18,000. A larger product with an admin panel, payments and integrations typically runs €35,000–70,000. We quote only after the workshop, because anything earlier would be guesswork.
- Scoping workshop and clickable prototype
- iOS and Android build from a single codebase
- App Store and Google Play submission
- CI/CD, crash monitoring and analytics
- Maintenance agreement with defined response times
Common questions
React Native for the large majority of business apps — one team, one codebase, releases twice as fast. Native when the app is built around continuous image or audio processing, or very specific hardware.
If you already have a system with an API, a thin middle layer is usually enough. If not, we build the backend as part of the project — it is a cost that has to be quoted alongside the app either way.
Always your company, under your own details. We guide you through Apple and Google verification, but the accounts must belong to the client — otherwise changing supplier means losing the app.
Realistically from €550 per month for monitoring, library updates and compatibility with new OS releases. Without it the app will stop working correctly within a year or so.
It starts with an audit
Tell us in two sentences what you want to achieve. We reply within one business day.