I liked Flutter 1.0, but then it broke my codebase with 2.0, and again with 3.0, which made me swear never to use it again.

The good ideas of Flutter, IMHO, got implemented in native Android (Kotlin + Compose).

▲

satvikpendem 3 days ago | parent [-]

I don't mind not having backward compatibility especially when it's for a growing framework that's not feature complete. Those versions are semantically versioned so you didn't need to upgrade if you didn't feel like it.

Jetpack Compose and Compose Multiplatform is nowhere near what Flutter does, it's essentially still Android only as their other OS support isn't really stable, even if they say it is. I tried to make an app and gave up and went back to Flutter.

	▲	palata 3 days ago \| parent [-]
		> Those versions are semantically versioned so you didn't need to upgrade if you didn't feel like it. This is only valid if you write a trivial app. If your dependencies migrate to the new major version, eventually you have to do it as well. Cross-platform frameworks are generally not terrible for trivial apps; the pain comes when the app get complicated. But then if it's a trivial app, I can write it natively in the different languages I need to support, so there is not much need for a cross-platform framework. Of course if your alternative is Qt, then Flutter is better :-).