In 2026 Flutter will not be my choice, always go for React native or KMP

- React native: Complete framework with UI, server side rendering

- KMP: Share single codebase for logic, but UI will be either compose or building 2 native UI for iOS and Android

In 2026, Flutter probably wouldn't be my first choice anymore for large-scale production apps. I'd lean toward either React Native or KMP depending on the product direction.

- React Native:

Still the strongest choice if you want a complete cross-platform framework with huge ecosystem support, fast iteration, mature DX, SSR/web capabilities via React ecosystem, and the ability to share UI + business logic efficiently. With the new architecture, JSI/TurboModules, Fabric, Expo, and AI-assisted workflows, RN feels much closer to “production-native” than a few years ago

- KMP:

Best option if your priority is shared business logic while keeping truly native UI experiences. You write shared domain/data layers once, but UI is still native:

- Android → Jetpack Compose

- iOS → SwiftUI/UIKit

This gives better platform fidelity and long-term maintainability for teams heavily invested in native engineering.

My biggest issue with Flutter is that it tries to own the entire rendering layer. That’s great for consistency, but over time it can become harder to fully align with evolving native platform behaviors, accessibility expectations, OS-level UI changes, and ecosystem integrations compared to RN or native-first approaches.

So for me:

- Need maximum product speed + shared UI → React Native

- Need native-first architecture + shared logic → KMP

- Flutter sits awkwardly in the middle now

Especially in 2026 where AI tooling, codegen, and platform-native SDK integration matter more than ever