Cross-platform app development

Cross platform app development that puts one codebase on iPhone and Android

We recommend the route that fits your team and your app in writing, then build it in accounts and a repository that belong to you.

Get a written route recommendation and scope
Trusted by the world's fastest-growing brands

What cross-platform means

Five routes to two stores, and how we pick between them

Cross platform app development is building one app for iPhone and Android without writing every screen twice. It comes in several forms, from sharing only the logic to sharing the whole app, and each form saves different work and costs different things.

FlutterReact NativeKMPPWANativeiPhone68%sign-ins32%Android9:41Book a slipOct 10Slip B-1440 ftBook B-149:41Book a slipOct 10Slip B-1440 ftBook B-14lib/

Five routes to choose from

React Native, Flutter, Kotlin Multiplatform, a web app on the home screen and two native apps are all ways to reach both stores. They differ in who can maintain the result and how close it sits to the phone.

Share what moves between phones well

Business rules, data fetching and many screens move between platforms well. Bluetooth, background work, payments sheets and permission prompts behave differently on each phone, and that work is not shared.

The choice is written down

Before any build starts you get a route memo that names the option we would pick, the one we would pick second, and the facts about your team and app that decided it.

Choosing the approach

Sharing the screens, or sharing only the logic

Both are cross-platform. They differ in how much of the app is written once, and so in what a change costs later.

Shared logicKotlin Multiplatform with native screensShared screensReact Native, Flutter or Compose Multiplatform
What is written onceBusiness rules and data handling, while each platform keeps its own screensScreens, navigation and business rules
Who builds itA shared-code engineer plus an iPhone developer and an Android developer for the screensOne team working in one framework, with a platform specialist on call for native pieces
How the app looksEach platform’s own controls and conventions by default, with two sets of screens to keep in stepConsistent on both phones, with room to follow each platform’s conventions where it matters
Cost of a new featureShared part built once, two screens built separatelyOne build, then testing on both platforms
A good fit whenThe company already has native developers and wants to share rules without changing how screens are builtBudget is tight, the design is the same on both phones and one team will own the app
When we would tell you not to go cross-platform

If the product is a camera pipeline, augmented reality, a game or a Bluetooth device with timing demands, two native apps are the safer route, and we would say so in the memo. If your users are all on one platform, one native app costs less than either.

The platforms and the frameworks

Six facts that shape a cross-platform decision

Each fact below names its source and the day we read it.

  1. KotlinGoogle

    Google supports Kotlin Multiplatform for sharing business logic between Android and iOS.

    Google’s Android developer pages call it stable and production-ready, and say you choose what to share, from core business logic to the whole app. Sharing logic does not require sharing screens, which keeps native interfaces on the table.

  2. Shared UIJetBrains

    JetBrains declared Compose Multiplatform for iOS stable in May 2025.

    The Compose Multiplatform 1.8.0 announcement says all major APIs are stable. The announcement cites the Respawn app sharing 96% of its code with Android. That is one app’s figure in the vendor’s own post, so read it as an upper bound.

  3. Web appsWebKit

    Push notifications reached web apps on the iPhone Home Screen in iOS 16.4.

    Apple’s WebKit team announced Web Push for Home Screen web apps with iOS and iPadOS 16.4 beta 1 on February 16, 2023. A permission request has to follow a direct tap, such as a Subscribe button. A web app can send alerts, but it reaches people through a Home Screen install, with no store listing.

  4. AppleXcode

    Apps uploaded to App Store Connect have had to be built with Xcode 26 since April 28, 2026.

    Apple’s requirement names an SDK for iOS 26 or later. Whatever framework wrote your app, its iPhone build is compiled in Xcode, so the framework version has to keep up with Apple’s periodic SDK minimum.

  5. Google Play16 KB pages

    Apps targeting Android 15 or higher must support 16 KB memory pages on Google Play from February 1, 2027.

    Android’s documentation says any app that uses NDK libraries, directly or through an SDK, has to be rebuilt for 16 KB devices. A cross-platform framework ships compiled native libraries inside the app, so in our reading the framework and plugin versions are part of the check.

  6. Existing appsFlutter

    Flutter can be added to an existing iPhone or Android app as a module.

    Flutter’s documentation describes building a Flutter module into a host app written in Swift, Objective-C, Kotlin or Java. It lists limits for mobile: only the multi-engine approach is supported, and packing several Flutter libraries into one app is not. A working native app can gain Flutter screens without being rewritten first.

The scope

What a cross-platform engagement produces

The work in six parts, each handed over as a document or a build.

Route memoFlutter chosenRouteTeamPhonesDesignDevice1Flutter2React Native3Kotlin MP4Two nativefitswith workweak

Route memo

A short written comparison of the routes that could fit, scored against your team, your users’ phones, your design and the hardware the app touches. You receive: the memo, with our first and second choice and the reasons.

Shared-code boundaryMappedWritten onceboth phonesBooking and paymentSlip map and tideSign-in and profileGate unlock rulesiPhone onlyPayment sheetSign-in buttonAndroid onlyPush promptBackground work

Shared-code boundary

A map of what is written once and what is written per platform, such as sign-in, payments, push setup and permissions. You receive: the boundary map, so nobody is surprised by platform work later.

Spike: Bluetooth unlock1 delayediPhoneiOS 26Older iPhoneiOS 17PixelAndroid 16Galaxy AAndroid 13DecisionKeep Flutter, native permissions

Spike on the hardest feature

A small throwaway build of the riskiest piece, such as Bluetooth, background location or a custom drawing, run on real phones before the scope is final. You receive: the spike result and the decision it led to.

RepositoryBuild 0.9 (14)Ttidewater-marina / member-appPrivateDartSwiftKotlinlib/shared screens and rulesios/iPhone-only code, markedandroid/Android-only code, markedREADME.mdsetup for a new developer

The cross-platform build

Both apps built from one codebase in the framework we agreed, with platform code kept in marked files. You receive: the repository in your organization and a README a new developer can follow.

iPhoneAndroid
Test log · build 0.9 (14)1 open16 of 17issues fixedStaff · iPhoneiOS 263/3Staff · PixelAndroid 162/227 members · iPhoneiOS 17 to 185/513 members · Galaxy AAndroid 13 to 146/7

Device and OS test matrix

Test builds on older and newer phones from both platforms, with issues logged and fixed or disclosed in the release notes. You receive: the test log and the open-issue list.

Upkeep plan2 dated changesXcode 26 SDKApr 28, 2026Today, Oct 816 KB pagesFeb 1, 2027AprJulOctJan 2027Xcode 26 SDK minimumWebzenia, in scope16 KB page supportWebzenia, in scopeStore accounts and codeTidewater Marina Co.

Upkeep plan

A dated list of the changes coming from Apple, Google and the framework, such as SDK minimums and target levels, with who handles each. You receive: the plan and a monthly written scope option for the upkeep.

How it runs

Decide, scope, test, release

Before the next stage begins, you approve the last one. The store accounts and the repository belong to you from day one.

xp-route-memo.csv

Route decision

Sample · Tidewater Marina Co. member app
RouteFitReason
FlutterChosenThe slip map and tide view are drawn once, and one team can keep both phones in step
React NativeSecondWorkable, but there is no JavaScript team or web app to share code with
Kotlin MultiplatformPossibleFits an in-house Android team, and would still mean two sets of screens
Web app on the home screenStaff onlyFuel-dock forms fit a web app. Members expect a store listing and a Bluetooth gate unlock
Two native appsNot nowTwo builds for 1,400 member households, 68% of sign-ins on iPhone
The gate unlock is tested first, on real phones, because it decides whether Flutter holds.

Our stack

The tools behind a cross-platform build

The frameworks we compare, and the tools that build, test and watch the result.

Flutter
Why Flutter

Flutter is Google’s toolkit for building iPhone and Android apps from one Dart codebase.

How we use it

We pick it when the design is custom and the same on both phones, and when no existing JavaScript team needs to share code.

Cross-platformPerformanceCodebase
FlutterOne
React NativeOne
Two native appsTwo

Questions

Cross-platform app development, answered

Start here

Get a written route recommendation and scope

Tell us where the app starts today. We’ll send back the route we would choose and the runner-up, what is shared and what is per platform, and a fixed price for the first milestone.