4 ms·
> -Flutter renders the UI itself rather than using native components, so you get the same experience on both iOS and Android. I thought this was an antipattern
by wwwigham 9y ago
> -Flutter renders the UI itself rather than using native components, so you get the same experience on both iOS and Android.
I thought this was an antipattern in modern mobile device Dev, since you're supposed to make your app "look and feel native" by always using native widgets where possible (and was a major argument for why, eg. Cordova was inferior to react native). Has the collective agreement turned on this, or it is simply contentious?
- mixmastamyk 9y agoPendulum swings. Similar to QT vs wxWidgets.
- solarkraft 9y agoI think it is changing. My personal opinion has definitely shifted, maybe partly because I'm tired of inferior Android experiences of the same app, but also because the looks of Android and iOS seem to be converging anyway. While maybe they couldn't before, many apps seemingly can now get away with one UX for both platforms - that is a strong simplifier and gives a potential branding advantage. It may be a good idea to still implement some "platform sensitive" widgets (some behaviors are still slightly different), but the demand for them seems to have drastically gone down.