Is Kotlin Multiplatform killing Flutter?

Thomas Middel
4 min readMay 24, 2024

The current options of cross-platform solutions are endless, and honestly: there’s no right or wrong. KMP and Compose look like a serious threat to Flutter, but is it something to be worried about or is there a significant difference that lets them exist side-by-side?

I’ll cut straight to the chase and say that I wouldn’t worry about it too much. For now…

It’s always one of those questions: “Why would you choose Flutter over…?“, “Is Flutter better than…?”, and I’ll always kindly say there is no wrong answer (as long as you don’t choose web-based frameworks like Ionic or Cordova, can you even call that mobile development?).

I love Flutter, but I won’t push it if it doesn’t make sense. If you have an existing product, tech stack, team, or just look at your own skillset, it might make more sense to use something like React Native instead, otherwise you’d have to hire new developers with Flutter knowledge, let your existing team go through training, or do a course yourself. It’s fun, but in business: it doesn’t always make sense.

Now, with Kotlin Multiplatform, we have yet another kid on the block wanting you to pick him first. But what would you even pick him for?