Web & Development
A mobile app, or only the feeling that you need one
We build native, cross-platform (Flutter, React Native) and PWA apps for companies with repeat customers. The first thing we tell you is whether you genuinely need a downloadable app, or just a well-built mobile site.
- Your customers order, book or subscribe repeatedly, not once
- You want to test a business model with a mobile MVP before investing heavily
- A competitor has an app and you are afraid of falling behind, but you are not sure it makes sense for you
01 · What it costs you today
You built an app, but users do not come back
The money is gone, and nobody knows whether the problem is the product, the technology, or simply that a downloadable app was never needed.
The original budget left maintenance out
At the next major iOS or Android release, the app started crashing or getting rejected on update. That is when you find out maintenance is not optional.
The wrong technology was chosen at the start
Native on both platforms, when cross-platform or even a PWA would have solved the same need. Now you are stuck with double maintenance costs you cannot stop without rewriting everything.
The app got rejected in review
Nobody on the team knows what the process involves, how long a resubmission takes or how to avoid it next time, and the launch date keeps slipping.
02 · What you get
A technology decision audit
A written recommendation: native, cross-platform, PWA or “not yet”, argued on cost and performance rather than assumed.
UI/UX design on each platform's guidelines
Aligned with the Human Interface Guidelines (iOS) and Material Design 3 (Android), with an interactive prototype before development starts.
Development in sprints, with test builds
Incremental delivery, not a big bang at the end. You see progress instead of waiting months for a surprise.
Testing on real physical devices
Not just emulators. Controlled beta testing through TestFlight (iOS) and the Internal Testing track (Google Play).
Publishing handled end to end
Developer account setup, store listing metadata, submission and active management of the review, including any rejections and resubmissions.
Maintenance under a monthly SLA
Mandatory updates at every major iOS and Android release, crash and performance monitoring, incident support.
03 · How we work
- 01
Audit and technology decision
1 to 2 weeks. We apply the decision framework to your specific case: usage frequency, hardware needs, the role of notifications, the monetisation model.
- 02
Discovery and specification
User flows, wireframes for the critical screens, the final technical stack, a sprint plan and a phased budget.
- 03
Design and development
The visual system, an interactive prototype, then the build in sprints, with builds delivered incrementally.
- 04
Publishing and maintenance
Testing on real devices, publishing handled in both stores, then updates at every major operating system release.
04 · Results
- CompanionTurkish Airlines
Part of the subcontractor teams on the airline's mobile app.
- Memento GroupAndroid app
A mobile app for the group's booking platform.
These are the figures reported by the clients themselves, for their own accounts, over the periods shown. We do not turn them into derived percentages and we do not present them as reproducible.
05 · What people usually ask us
- “I want native, so it is the best.”
- Honestly: native is only technically best when the technical need is there, heavy graphics, niche hardware, very large scale. Otherwise the performance difference a user actually perceives is negligible next to the cost difference. We recommend native only when the audit criteria genuinely call for it.
- “It is too expensive.”
- Compare the cost of the wrong technical choice, dual-platform native when it was not needed, followed by double maintenance forever, with the cost of getting the decision right from the start. On tight budgets, cross-platform or even a PWA delivers 90% of the functional result at a fraction of the cost of a full native build.
- “I tried it with a freelancer and it did not work.”
- The most common risk is not the initial code quality, it is continuity: who maintains the app when the developer becomes unavailable in exactly the month Apple or Google forces an update. We deliver with handover documentation and an explicit maintenance SLA.
06 · Frequently asked questions
- How much does a mobile app cost?
- A focused MVP starts from 25,000 EUR, a complete product with multiple roles and integrations reaches 70,000 to 200,000 EUR. The big difference comes from the technology choice: dual-platform native costs 1.5 to 2 times more than cross-platform.
- Do I really need a native app?
- Rarely. Cross-platform (Flutter, React Native) delivers 90%+ of native performance at 40% to 60% of the cost for most business apps. Native is justified only for heavy graphics, niche hardware or very large scale.
- Do I actually need an app, or is a mobile site enough?
- If your user interacts occasionally, one booking, one informational visit, a fast mobile site converts better than an app they will never install. An app is justified by frequent use, essential notifications, or a need for offline or hardware access.
- How long does publishing on the App Store and Google Play take?
- On first submission Apple usually takes 3 to 7 days, Google is similar. A rejection on the first pass is common and normal, we handle it as part of the process, not as an emergency.
- What happens if I skip maintenance after launch?
- Apps without maintenance tend to break within 12 to 18 months, as the annual iOS and Android updates change permissions, APIs and review requirements. Maintenance is not optional, it is a recurring budget line.
Shall we talk about your project?
Tell us where you stand. If we are not the right answer for you, you will hear it in the first conversation.
Request a quote