> But these have all the same problems eventually.
I've maintainted a Flutter app and it's 10% of the maintenance of a normal Android or iOS app. The only real breaking change they had in 6 years was the switch to strict typing.
I've maintainted a Flutter app and it's 10% of the maintenance of a normal Android or iOS app. The only real breaking change they had in 6 years was the switch to strict typing.
One related to this: https://docs.flutter.dev/release/breaking-changes/android-ja...
We had a bunch of sdk users who couldn't port over our Android sdk because of "Unsupported class file major version 65" so we ended up making a flutter plugin for them rather than downgrading the native Android versions. I would expect many sdk devs to not care enough to do this, especially the open source ones.
All the changes on these platforms have been done thanklessly by someone. Before this, someone was paid to do it, so they might not need the thanks. But I saw how fast Cordova unraveled after Apache announced they were dropping support.
There's the frameworks like GetX too which have slowed down recently. We've been removing them from the code and replacing them.
Rendering everything to a canvas has disadvantages but also advantages. Flutter doesn't need to care about most framework changes.
How does rendering to canvas insulate you, for example, from the underlying permissions changes in the Android platform?
Android went from a free for all to considering that maybe we should ask the user before granting full access to all of their files without warning. In addition, the upgrade paths are well documented, and give you multiple years to migrate.