Interactive guide · 2026 edition

Mobile Tech Stacks, Visualised

A mind-map view of the 2026 mobile universe — cross-platform, native, UI, navigation, state management, data, testing, build tools, push notifications, and design. Pick your stage, filter by what matters, and see the stack that fits.

/ search 1-4 stage Esc reset

The landscape at a glance

— · click a node to jump to its card

Which stage are you at?

Pick one — the stack below adapts, and cards fade to only what fits.

All technologies

Decision cheat-sheet

Pick by team

  • Web devs: React Native + Expo. Familiar React patterns, great DX, fast iteration.
  • Dart enthusiasts: Flutter. Pixel-perfect UI, single codebase for mobile + web + desktop.
  • Native-first with shared logic: Kotlin Multiplatform (KMP). Native UI per platform, shared business logic.
  • iOS-only: SwiftUI. Apple-first features, modern declarative syntax.
  • Android-only: Jetpack Compose. Modern Kotlin, Google-backed, great tooling.
  • Enterprise .NET: .NET MAUI. C# everywhere, Visual Studio integration.

Pick by constraint

  • Fastest to market: Expo. Managed workflow, EAS builds, OTA updates.
  • Best performance: Native (SwiftUI / Jetpack Compose) or Flutter.
  • Smallest team: Expo or Flutter. One codebase, both platforms.
  • Offline-first: Firebase + Realm / WatermelonDB. Built-in sync.
  • Web + Mobile: React Native + Expo for web. Universal codebase.

Anti-patterns to avoid

  • Ejecting from Expo too early. The managed workflow handles most use cases.
  • Building custom navigation from scratch. Use Expo Router or React Navigation.
  • Ignoring platform conventions. iOS and Android users expect different UX patterns.
  • Shipping without crash reporting. Add Crashlytics before your first beta.
  • Using web-only state management patterns. Mobile has different lifecycle needs.
  • Skipping deep linking setup. It only gets harder to add later.
Tweet Reddit LinkedIn Star on GitHub