Skip to main content
Fugen Services logo

Mobile Apps

One codebase, both stores, without the usual compromises

Cross-platform is the right default for most business apps: you maintain one codebase, ship to both stores, and spend the saving on the product instead of duplicating it. The craft is in knowing which parts still need platform-specific treatment.

Indicative

From £22,000

Fixed price agreed in writing before any build starts.

Get a quote+44 7488 265083

Background photo by Gül Işık on Pexels

The problem this solves

Done badly, cross-platform produces an app that feels foreign on both platforms — Android back behaviour on iOS, iOS pickers on Android, and animation that judders. The saving disappears into support tickets and bad reviews.

What you get

Framework recommendation

Flutter or React Native chosen on the basis of your feature set, your team’s existing skills and hiring plans — since you will maintain this after we hand it over.

Platform-adaptive UI

Shared logic with platform-appropriate navigation, controls and gestures, so it reads as native on each.

Native modules where needed

Swift or Kotlin written directly for the parts the framework does not cover well — camera pipelines, background location, hardware SDKs.

Shared business logic and tests

Validation, state and API handling written once, with automated test coverage.

Both store submissions

App Store and Play Store listings, compliance and review handling for both.

Over-the-air updates

Where store policy permits, JavaScript-layer updates so content and logic fixes ship without a full review cycle.

How we work

  1. Scope and framework choice

    Written recommendation with trade-offs stated, fixed price.

  2. Shared architecture

    Set up state management, navigation and the API layer.

  3. Build

    Two-week cycles with builds on both platforms every cycle — never one then the other.

  4. Device testing

    Real iOS and Android hardware across performance tiers.

  5. Dual submission

    Both stores prepared and submitted together.

  6. Support

    Thirty days included, then a joint maintenance plan.

What you should expect

  • Single codebase serving both stores
  • Typically 30–40% less than two native builds
  • Platform-appropriate navigation on each OS
  • Native modules only where they are genuinely needed

Built with

  • Flutter
  • Dart
  • React Native
  • TypeScript
  • Expo
  • Riverpod
  • Firebase
  • Swift
  • Kotlin
  • Fastlane

Mainstream, well-supported technology — chosen so you can hire for it and so another team could take the project over.

Cross-Platform Apps — your questions

Including the ones about cost, which most agencies leave off the page.

Flutter gives more consistent rendering and stronger performance for animation-heavy interfaces, but Dart is a smaller hiring pool. React Native lets a team that already writes React share skills and some code with your web app. If you have React developers, React Native usually wins on total cost of ownership; otherwise Flutter is the safer technical bet.

For the vast majority of business apps the difference is imperceptible. It becomes real in heavy 3D, sustained camera processing or complex continuous animation. If your app does those things we will recommend native for that part or entirely, rather than pretending the gap does not exist.

Typically 30–40% against two native builds, and the larger saving is ongoing: one codebase to maintain, one set of features to keep in sync. The saving shrinks if your app needs lots of platform-specific native work, which is something we assess during scoping.

Partly. Both frameworks can target web, and business logic is genuinely reusable, but interfaces designed for touch rarely translate well to desktop. We normally share the logic and API layer and build a proper web front end separately.

Talk to someone who has built this before

A short call is usually enough to tell you whether this is the right service for your situation — including when it is not.