Expo vs Kotlin (Jetpack Compose) in 2026: Which for Your Android App?
Expo SDK 58 (React Native 0.88) vs Kotlin 2.3 + Jetpack Compose. We ship the same app on both: ~16k lines of TypeScript vs ~21k of Kotlin, OTA, Play APIs.
Expo vs Kotlin is the Android version of the "React Native vs native" question. In 2026 both sides are strong. Expo shipped SDK 58 on October 15, 2026, on React Native 0.88. Native Android means Kotlin and Jetpack Compose, and Compose is now Google's recommended way to build Android UI, with Material 3 and a regular BOM release train.
We ship the same app on both. The SoarStarter Expo template and Kotlin template implement the same product: Supabase auth (email and Google), RevenueCat subscriptions with a paywall and account-bound entitlements, push notifications, onboarding, consent and biometric-lock gates, an update gate, PostHog analytics, Sentry crash reporting, English and Chinese localization, and the same example features on the same Supabase backend. Here's what that shows about Expo vs Kotlin.
Quick verdict
| Expo (React Native) | Kotlin + Jetpack Compose | |
|---|---|---|
| Current version (Nov 2026) | Expo SDK 58, React Native 0.88 | Our template: Kotlin 2.3, Compose BOM 2026.05, AGP 9.2 |
| Language | TypeScript + React | Kotlin |
| Platforms from one codebase | Android, iOS and the web | Android (our template's minSdk 26 = Android 8.0, targetSdk 37) |
| Our app's size in code | ~16,000 lines of TypeScript | ~21,000 lines of Kotlin |
| Shipping fixes | OTA JavaScript updates via expo-updates | Play Store release; Play In-App Updates prompts users |
| Google Play APIs | Through Expo modules and libraries | Direct: In-App Updates, In-App Review, Credential Manager, FCM |
| Architecture in our template | Expo Router, TanStack Query, Nativewind | MVVM, Hilt, Coroutines + Flow, DataStore |
| Best fit | Teams that need Android and iOS, React developers | Android-first products, Android specialists, deep platform work |
Short answer: choose Expo when you need iOS too, or your team writes React. Choose Kotlin and Jetpack Compose when Android is your main platform, you want direct access to Google Play and Android APIs, or you're hiring Android specialists.
The line count
We counted the app code in both templates (main source, no tests). The Kotlin app is about 21,000 lines of Kotlin across 176 files. The Expo app is about 16,000 lines of TypeScript, and those lines also ship the iOS app and a web build.
The Kotlin side is larger partly because native Android is explicit. Hilt modules, ViewModels, StateFlow plumbing, and a typed repository layer are all code you write. That explicitness is also why the Kotlin codebase is easy to navigate and test: every dependency is injected and every screen state is a type. The Expo version gets similar structure from fewer lines, using hooks and TanStack Query.
If you only need Android, the size difference doesn't matter much. Once you need iOS too, it matters a lot. The native route means a second codebase (our SwiftUI template is another ~15,000 lines), while Expo needs only small per-platform adjustments.
Developer experience
Expo is web-style development for mobile: file-based routing with Expo Router, Tailwind classes through Nativewind, instant reload, and EAS Build in the cloud. You can build an Android release without opening Android Studio. A React developer is productive in days.
Kotlin and Compose is Google's recommended path. Our Kotlin template uses MVVM with Hilt for dependency injection, Coroutines and StateFlow for state, DataStore for preferences, and supabase-kt for the backend. Android Studio's Compose previews, Kotlin's null safety and Gradle's tooling are excellent, but there's more to learn, and a Gradle build takes longer than a Metro reload.
Google Play integration: Kotlin's home turf
On Android, native code talks directly to Google Play and the Android SDK. Our Kotlin template uses:
- Play In-App Updates for its update gate, so users can update without leaving the app.
- Play In-App Review for rating prompts.
- Credential Manager for Google sign-in.
- Firebase Cloud Messaging through a
FirebaseMessagingServicefor push.
The Expo template covers the same needs with Expo modules and libraries: expo-notifications, expo-store-review, a Google Sign-In library, and a version check that sends users to the store. They work well. The difference shows up at the edges, for example the newest Android APIs, home-screen widgets, foreground services, or a vendor SDK that ships only for Android. In Expo, those mean waiting for a module or writing native Kotlin anyway.
Shipping and updates
Expo's over-the-air updates are its biggest operational advantage. Our Expo template ships expo-updates with a fingerprint-based runtime version, so JavaScript and asset fixes go straight to users, while native changes automatically require a new build (EAS build guide).
On native Android, every fix is a Play Store release. Play reviews are usually quick, and staged rollouts let you limit the blast radius. In-App Updates can even force a critical update from inside the app. But a staged rollout isn't the same as fixing a bug in ten minutes.
Going cross-platform from Kotlin
There's now a Kotlin answer to cross-platform too. Compose Multiplatform for iOS has been stable since May 2025, so you can share Kotlin UI and logic with iOS. It's a serious option for Kotlin-first teams. Our Kotlin template is a native Android app and doesn't use Compose Multiplatform, so if you need iOS from one codebase today, Expo is our ready-made path.
How to choose
- Choose Expo if you need Android and iOS (or the web) with one small team, your developers already write React, or OTA fixes matter to your release process.
- Choose Kotlin and Jetpack Compose if Android is your primary or only platform, you need direct Google Play and Android APIs, or your team is made of Android specialists.
- Comparing iOS too? See Expo vs SwiftUI, or the Expo vs native (SwiftUI / Jetpack Compose) overview of all three stacks.
Both templates share one Supabase schema and one RevenueCat entitlement model, so you can start with one and add the other later on the same backend (Expo backend modes, Kotlin backend modes). Read the Expo docs and Kotlin docs, then compare the Expo template and the Kotlin template.