Mobile App Development

End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week.

It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week.

Because hours are the wrong metric. If we’re optimizing for hours billed, we’re not optimizing for your outcome. The deal is simpler: every week, we earn the next one. If we don’t, you don’t pay. We’re free to spend zero hours or sixty. What matters is whether you’re blown away.

We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves.

Default to React Native or Flutter when feature parity with web matters, time-to-market is critical, or the budget can’t support two codebases. Native (Swift, Kotlin) when the app is graphics-heavy, hardware-sensor-heavy, or needs absolute UI fidelity. We’ll show you the trade-offs on a real estimate, not push you toward what’s easiest for us.

End-to-end: store metadata, screenshots, video previews, age ratings, privacy declarations, App Tracking Transparency, App Privacy labels, and the review-rejection cycle. We’ve shipped through both stores enough times to know the rejection reasons before they happen.

Yes, and we strongly recommend it. Mobile apps need OS-version maintenance (every iOS/Android release breaks something), library security patches, and store-policy updates. We offer post-launch retainers ranging from on-call hotfix to active feature development. You’re never forced into one; you pick the level.

Yes, by default. Firebase Cloud Messaging or OneSignal for push, Mixpanel/Amplitude/PostHog for analytics, Sentry or Bugsnag for crashes, and a privacy-respecting analytics path (we lean toward Umami/Plausible on the web equivalent). Configured before launch, not after the first incident.

Cross-platform (React Native or Flutter) MVP with login, core flow, and one paid feature: €25-50k. Production mobile app with backend, push, in-app purchases, and analytics: €50-120k. Two true-native (Swift + Kotlin) codebases shipped in parallel: 1.7-2.2x the cross-platform number. Apple and Google developer account fees are €99/year each and not included. We quote App Store and Play Store rejection-cycle work into the budget so a ‘we’re done’ moment isn’t followed by three weeks of resubmissions.

When you don’t need camera or sensor access beyond what the browser exposes, your audience uses both iOS and Android, App Store revenue isn’t core to the model, and you want one codebase that ships in hours not days. PWAs handle offline, push (on Android), home-screen install, and most modern web APIs. We push back on ‘we need a mobile app’ when a PWA would ship 6 weeks earlier and convert the same users. We build native when OS integrations (HealthKit, ARKit, secure enclave, background workers, deep system access) are load-bearing.