And like... there are even serious issues on Android, stemming from a massive argument about how the core developers of Flutter don't want to support synchronous callbacks into the Dart isolate even though there are tons of Android lifecycle APIs that fundamentally require synchronous delegates :/. This issue is so serious that it supposedly makes Flutter entirely unusable on many Android devices, as it can't react to memory pressure requests (which means activities get destroyed) but also is unable to implement the save/restore state mechanism (so views come back either in subtly wrong ways or even entirely broken); and so people have been reporting that it is literally impossible to use the photo picker on smaller Android devices (as that is a widget that deterministically causes memory pressure).
https://github.com/flutter/flutter/issues/6827 (opened Nov 2016) https://github.com/flutter/engine/pull/4358 ("closed" due to being rejected)
Essentially, I highly encourage anyone attempting to use pretty much anything to sit around and read through the open issues and look at what is currently being built vs. what is still on the roadmap, as the marketing messages behind a lot of these projects might say "we now support so many more iOS controls and it is amazing" while the reality on the ground is that the controls they have might only sort of work and the things that you need might not only not yet be done but might be on the list of things that the project has some philosophical aversion to (which is the case with the Android issues there: if any of those things will cause you a problem, you might be waiting for years to see fixes for them, as the obvious fix was rejected).
It makes me wonder if the flutter team is aiming to totally replace native apps or replace 'most' native apps, because I tend to agree with Hixie re the synchronous calls, but only in 90% of app use-cases.
The iOS text stuff is surprising, though, especially since the last beta release had a 'Pixel Perfect Cupertino' focus. Hopefully will be fixed before they bring out 1.0
I've been thinking about trying flutter for a fun little side project; now I'm going to browse through open issues and see if anything seems like a showstopper. hope not because flutter seems neat and RN scares me.
Also, this should really be a top comment.
Just letting you know we haven't forgotten about these issues and will be getting to them in the coming months. The iOS text issues, specifically, have someone looking into them sooner rather than later.
This, in particular, even with Google-level attention and resources, seems like a design dead end, at least for third party apps.