I won’t be recommending that anyone use Dart or Flutter on new projects.
You seem to think Google cares at all. Android has been languishing and Flutter is lightyears ahead. KMP is junk compared to what Flutter has accomplished with a fraction of the bells and whistles.
You seem to think Google cares at all.
Odd conclusion to draw. I’m simply not inclined to recommend tools that are not going to be supported by the organization that created them. Development ecosystems are important when planning a project.
What I mean to say is that Google isn’t invested in native android either. It’s been repeatedly strip mined by first-timers looking for a quick promotion and left to burn.
Things got so bad that Google gave up on native Views and created Jetpack Compose, which has been a source of many complaints related to performance.
In 2024 Flutter has instant hot-reload, and the “native” (but 100% bundled) solution still requires a complete reinstall on the device. In fact, Dart can compile to native code (or JIT) without an issue, yet Kotlin Native is barely in GA in the new compiler support has been lagging while the new compiler isn’t out of beta and is still poorly supported by tooling.
Consider the absurdity: React Native is the only true native framework out of RN, Jetpack Compose, and Flutter. And all of this barely scratches the surface of the tooling problems that Flutter 99% avoids by allowing development on desktop, web or iOS simulator.
