03 / SERVICE

Mobile App Development

An app that behaves correctly offline, on real devices — not just in a simulator.

from €16,900

The Problem

Mobile isn't web with a smaller screen. Offline behaviour, device APIs, app-store review, and platform-native conventions are a genuinely different discipline — one a generalist web team routinely underestimates until the first rejected submission.

  • An app that works perfectly on Wi-Fi in the office and falls over in the field with no signal
  • A build that passes every internal test and still gets bounced by App Store review
  • An interface that "ports" a web layout instead of respecting how iOS or Android actually work

What's Included

Offline-first data handling

where the use case needs it — sync, conflict resolution, local storage, specified up front.

Native device APIs used correctly

camera, location, push, biometrics — not simulated web equivalents.

Platform-native UX conventions

for iOS and Android, not one design forced onto both.

App-store submission handled end to end

including the review checklist most teams discover the hard way.

A backend/API layer scoped to mobile constraints

(payload size, retry logic, battery cost).

Who It's For

Perfect for

  • Product teams building a field-service, logistics or consumer app with real offline needs
  • Founders whose product is mobile-first, not a web app with an app wrapper
  • Teams adding a mobile companion to an existing web product

Outcomes

  • An app that works correctly with no signal, not just a spinner and an error
  • A submission that passes store review the first time, because the checklist was built in
  • A codebase your own mobile engineer (present or future) can maintain

Packages

TIER 01

Single-platform App

One platform, done properly — iOS or Android, your choice.

from €16,900

→ 8–10 weeks · starts within 3 weeks

  • Specification covering offline behaviour, device APIs and platform UX conventions
  • Native build (Swift for iOS, Kotlin for Android) or React Native for a shared logic layer
  • App-store account setup guidance and submission handling
  • Backend/API integration, scoped to the app's needs
  • Source code and documentation, transferred on final payment

BEST FOR A defined single-platform user base — internal field teams on company-issued devices, for example.

Most chosen

TIER 02

Cross-platform App

iOS and Android from one codebase, native where it counts.

from €21,900

→ 10–12 weeks · starts within 3 weeks

  • Everything in Single-platform App, built for both stores
  • React Native architecture with native modules where a platform API demands it
  • Submission handled for both App Store and Google Play
  • Source, documentation and credentials, transferred on final payment
  • 30 days of post-handover bug-fix cover

BEST FOR Consumer or field apps that need both platforms without duplicating the whole build.

TIER 03

App + Backend

The app and the backend/API it depends on, built together.

from €33,500

→ 14+ weeks · starts within 4 weeks

  • Everything in Cross-platform App
  • A backend/API built specifically for the app's data and offline-sync needs
  • Push notification infrastructure and authentication
  • Phased delivery with demo milestones, source transferred on final payment

BEST FOR A mobile product launching with no existing backend to integrate against.

See all packages →

How This Engagement Runs

Survey

We read the device constraints, the environments the app runs in (connectivity, hardware), and any existing backend APIs it needs to talk to.

Specification

Platform choice, offline strategy, and API contracts are written down and priced.

Build

Weekly increments, demoed on real devices, not just a simulator.

Verification

Tested against real network conditions and the store review checklist before submission.

Handover

Source, store-account access notes and documentation transfer on final payment.

See the full Build Log →

Capability Example

An illustrative engagement, written from how we work. Client details are withheld and no outcome figures are claimed.

What we build with

  • React Native
  • Swift
  • Kotlin
  • TypeScript
  • Firebase
  • REST / GraphQL
  • App Store Connect
  • Google Play Console

Frequently asked

Native or React Native — which do we need?
If the app leans heavily on one platform's specific hardware or a demanding UI, native. For most field-service and consumer apps spanning both stores, React Native ships faster without a real quality tradeoff — we recommend one in the Discovery/Specification stage, not before.
What happens if the app is rejected by App Store review?
Resubmission after an addressable review rejection is covered within the delivery window stated in your package; it's built into the specification's testing pass, not treated as scope creep.
Do you handle app-store accounts, or do we need our own?
You keep your own Apple Developer and Google Play accounts (they’re tied to your company, not ours) — we guide setup and handle submission within them.
Can the app work fully offline?
Depends on the use case — full offline with sync-on-reconnect is a common requirement for field-service apps and is scoped explicitly in the specification, including how conflicts are resolved when two changes happen offline.

An app tested against real devices, not a demo environment.