There are pretty much the same questions all the time in the air around Flutter and people who want to try Flutter and are unsure should they or not. Questions like “is Flutter better than X?”, “Can Flutter do things like Y”, “How I get my Z-person to accept Flutter to project” etc.
I say, just try it. Do something with it. Document it. Show proof-of-concept to customer/boss/anyone. See if they like it. For this project Flutter was totally the right choice, and I was able to prove it with hard work. It was relatively easy to jump from Java/Kotlin/Swift-world to Dart-world.
My thinking went from “Yeah sure, again new cross-platform which will die in a year” to “Oh my god this is the best thing ever happened in the world”.
But Flutter isn’t even nearly perfect. As an example, my personal opinion about localization is that it is made way too rough and slow. It wasn’t hard at all, but it just took way too much time. There are also a lot of small issues, but they are getting fixed one by one.
Thankfully Flutter is open source and the community is pretty active implementing new packages for doing native things on Flutter-side. But because everything is open source, there are a lot of packages that A) doesn’t have support for iOS or B) are not maintained. It will be interesting to see where Flutter goes from here when the community starts to grow and more people join helping others.
On December 4th, at Flutter Live event in London, the Flutter 1.0 was announced. Tim Sneath’s post about the release summarizes well the aspects why also I have found Flutter interesting: tool to build a beautiful app, fast, productively and with open source mentality.