3 ms·

What about Fluter?

• ryanwaggoner 9y ago
  Even more skeptical, especially since it hasn't caught on yet. Now I have to learn Dart, trust that Google doesn't kill Flutter, trust that they'll give it their full support even though they're also supposed to be safeguarding and advancing native Android dev, etc. Plus, I still have to deal with all the issues that any hybrid or psuedo-native solution adds. Things like feature lag, crappy and non-native UI / UX, more pain during debugging / optimizing, extra layer of bugs to deal with, lower community and support, etc, etc. Just learn Swift! It's not that hard! :)
  • 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 ago
      Agreed, that's my "crappy and non-native UI / UX" point :)
      • on_and_off 9y ago
        Right 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.