2 ms·
All good points. Also accessibility is not great with flutter right now as they don’t wrap native components. They take a qt like approach, I.e they attempt to
by htormey 9y ago
All good points. Also accessibility is not great with flutter right now as they don’t wrap native components.
They take a qt like approach, I.e they attempt to simulate these native components.
- ryanwaggoner 9y agoAgreed, that's my "crappy and non-native UI / UX" point :)
- on_and_off 9y agoRight now it more feel like 'uncanny valley' native. They don't look as bad as a rendered webview, but they look distinctively different from the native implementation. For example on Android, the ripple implementation is very different on Flutter. It might even be that Flutter more closely adheres to the design spec, but since what I am used to is the actual Android implementation, the Flutter one feels wrong. On top of some missing features like accessibility. Perfs are also not entirely where they are promised, but that's a separate issue.