If you want cross platform with a nice set of mature libraries and components, have a look at Delphi. It now (optionally) uses Skia as its rendering engine, the same as Flutter.
Is Kotlin Multiplatform Replacing Flutter?
11–20 of 80 posts
Re: Is Kotlin Multiplatform Replacing Flutter?
#12One datapoint is that Google rewrote their Google Docs app in KMM (which doesn't include UI, that's Compose Multiplatform), replacing their legacy in-house framework. They intend to write more of their apps in it.
They also recently offshored some Flutter roles which may be a sign of how central they view Flutter. In a few years it may be in the graveyard.
https://touchlab.co/KMP-at-google
https://www.reddit.com/r/FlutterDev/comments/1chwqtu/flutter...
Re: Is Kotlin Multiplatform Replacing Flutter?
#13Flutter has the challenge that it requires a dedicated language (Dart) and ecosystem to execute "on top" of each native platform it aims to support. Flutter skills can only be used to build Flutter things.
Kotlin Multiplatform (KMP) on the other hand, as the name suggests, allows one's knowledge in Kotlin/Android/JVM (a vastly bigger and more established ecosystem) to be used for building cross-platform apps.
KMP's focus is on reusing "logic" while implementing each platform's UI using the platform specific framework (SwiftUI and Jetpack Compose for mobile). I see this as a big advantage as well, as it allows apps to keep up with each platform and feel "at home", instead of landing with an "averaged" experience.
So yes, KMP is a more sustainable path forward.
Re: Is Kotlin Multiplatform Replacing Flutter?
#14If you want cross platform with a nice set of mature libraries and components, have a look at Delphi. It now (optionally) uses Skia as its rendering engine, the same as Flutter.
Is it better than WinDev? It looks like a similar kind of product.
Re: Is Kotlin Multiplatform Replacing Flutter?
#15I really see zero compelling evidence of this whatsoever. It seems like some random bullshit Twitter drama without any substance behind it.
Please consider that many of us have been burned before. I've been in business for over 25 years now and I am still supporting several apps built with now forsaken technologies. That includes a web app built with Dart back when Google claimed that its Dart VM would be bundled into every browser.
Now, I like Flutter and I like Kotlin. Jetpack Compose is really nice. But if I am starting an app today and in a year or two, Google decides that developing two competing frameworks is too expensive, they'll discontinue one. If it is the one that I chose, I'll be sooooo bitter.
So yes, right now, they're pushing both and they claim not to have a preference but we need some reassurance that it'll stay that way.
Re: Is Kotlin Multiplatform Replacing Flutter?
#16For desktop targets you still have to bundle the whole JVM as I understand.
Re: Is Kotlin Multiplatform Replacing Flutter?
#17Since when was Flutter the "go-to solution for cross-platform development"? Maybe for hobbyists but in the corporate space it's still React Native. The problem with Flutter, and this extends even further with KMP is that the scope of your skills is limited to making mobile apps whereas with React Native you are learning and using skills that can apply to a complete stack. KMP is even worse in this regard as they expe…
Unlike RN, Flutter is desktop worthy.
Re: Is Kotlin Multiplatform Replacing Flutter?
#18To resolve the long-standing issues of naming inconsistency and abbreviation confusion that have puzzled many Kotlin developers over the past two years, we are deprecating the “Kotlin Multiplatform Mobile” (KMM) product name. From now on, “Kotlin Multiplatform” (KMP) is the preferred term when referring to the Kotlin technology for sharing code across different platforms, regardless of the combination of targets being discussed.
From: https://blog.jetbrains.com/kotlin/2023/07/update-on-the-name...
Re: Is Kotlin Multiplatform Replacing Flutter?
#19[deleted]
Re: Is Kotlin Multiplatform Replacing Flutter?
#20Maybe I'm getting cynical but in terms of longevity, I don't know how long JetBrains will be around and I'm not trusting Google to maintain a project for a long time. Can't believe I'm saying this but for perennial projects in that sphere, Java seems like the better option :/