Native or Cross-Platform Mobile Apps: Swift, Kotlin, Flutter and React Native

Most products need an app on both iOS and Android, and the first architectural decision is whether to build two native apps or one cross-platform app. Swift with SwiftUI and Kotlin with Jetpack Compose are the platform-native routes. Flutter and React Native share one codebase across both. Kotlin Multiplatform sits between them, sharing logic while allowing native or shared UI. Each produces good apps in the right hands, and the trade-offs are specific.

At a glance

Swift
The Apple language for iOS, with SwiftUI as its current declarative UI framework.
Kotlin
The preferred language for Android, with Jetpack Compose for declarative UI.
Flutter
A Dart framework that draws its own widgets for a consistent look on both platforms.
React Native
A JavaScript or TypeScript framework that renders through native platform views.

The problem

Two native apps double the implementation and testing effort, and keeping features, fixes and behaviour aligned between two codebases takes deliberate coordination.

A cross-platform app saves that effort for the shared parts but adds a layer between the app and the operating system. Bluetooth, background execution, notifications and new platform features may need native code anyway, and the plugins that provide them vary in quality and maintenance.

Share code where the platforms behave alike, and go native where they differ. Device communication is usually where they differ most.

Apps that talk to hardware

Companion apps for connected devices depend on Bluetooth Low Energy, Wi-Fi provisioning, background operation and sometimes NFC. iOS and Android handle each differently, particularly permissions and what an app may do in the background. Cross-platform frameworks reach these features through plugins or native modules, which need the same scrutiny as any other dependency.

A common pattern is a shared UI with a thin native layer for device communication, written in Swift and Kotlin and exposed to Flutter or React Native. Kotlin Multiplatform reverses the split, sharing logic such as protocol handling while the UI can stay native.

What good looks like

List the platform features the app depends on, especially Bluetooth, background tasks, notifications and payments, and check how each framework supports them.

Assess the team: existing web and TypeScript skills favour React Native, while separate iOS and Android skills favour native or Kotlin Multiplatform.

Build a proof of concept of the riskiest feature on both platforms, on real phones, before committing to a framework.

Mobile development approaches
ApproachLanguageUICode shared
Native iOSSwiftSwiftUI or UIKitNone with Android
Native AndroidKotlinJetpack Compose or ViewsNone with iOS
FlutterDartOwn rendering engineUI and logic
React NativeJavaScript, TypeScriptNative platform viewsUI and logic
Kotlin MultiplatformKotlinNative, or shared with Compose MultiplatformLogic, optionally UI
All five are actively maintained and used in production apps.
Two native apps and one cross-platform app
Two native appsOne cross-platform app
Platform feature accessDirectThrough plugins or native code
Development effortRoughly doubleMostly shared
New OS featuresAvailable on releaseMay wait for framework support
Consistency between platformsNeeds coordinationLargely automatic
TeamTwo skill setsOne main skill set
Where each approach has the advantage.

What it changes

Shared Effort

Cross-platform code ships features to both platforms together when the app suits it.

Platform Fidelity

Native code gives full access to platform features and the expected look and feel.

Reliable Device Links

Bluetooth and background behaviour are proven on real phones, not assumed.

Maintainability

A framework the team knows well is easier to keep current through yearly OS releases.

Where to go next

Plan for annual iOS and Android releases. Each changes permissions, background rules or store requirements, and native and cross-platform apps alike need updating to keep pace.

Keep business logic and protocol code in a well-tested layer, whatever the framework. It is the part most worth sharing and the most expensive to get wrong.

Problems this prevents

  • Features drifting between two native apps
  • An unmaintained plugin for a critical feature
  • Bluetooth behaviour that differs by platform
  • A framework the team cannot support long term

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.