While I agree that the bug fixing capabilities of the flutter team could be improved, it‘s still reasonable to assume that they‘re primarily caring about Google‘s issues - given Google pays the party.
Still, you comparison isn‘t really a good fit IMHO because it seems you’re „just“ wrapping html content into the native ecosystem, which defeats somehow the purpose of actual native apps.
And even if you‘ll only target iOS I‘d say Flutter is still a more pleasant and more productive tech to use compared to f.e. SwiftUI - of course this only applies for actual native code.
Still interesting to read, thx for the article.
I might modify the title though since I wouldn’t consider a html wrapper a native app you‘re migrating to flutter.
In OP’s use case he describes the purposes of the having the html content wrapped in an app: easy access in an emergency.
I am curious as to why the tech community feels so strongly against html content wrapped as an app. There is a lot of valuable reference content which would benefit from being freed from the rigid structure of an ebook, and so suit an app very well, but doesn’t need ‘native’ functionality per se. Putting that content into PWA makes it harder to monetise. App distribution model works well.
hits me too and it‘s really annoying... I even got used to quit Mail.app but yeah... it‘s bad.
My feeling though is that google is more and more saying goodbye to standards... just a feeling
These chemicals are still used in the countries they're shipped to. If there was no revenue in cannabis, it would only change the fact that people are clandestinely growing it in American forests—tons of agriculture worldwide would still be impacted.
