Flutter Revisited

Last year I took a quick look at Flutter, and decided to keep an eye on it and see how it matures. Here are my current thoughts.


Since my first look, Flutter has come out of beta, and released 1.0 as stable. As I write, the stable version is 1.7, and Flutter for the web, or Hummingbird, is under active development.

3rd Party Libraries

I don’t think I’ve ever written an Adroid app using only 1st party libraries. 3rd party libraries exist to take the rough edges off the Android APIs, to interface with 3rd party APIs and services, and generally make development easier.

3rd party libraries for Flutter are appearing as the Flutter developer community grows. One potential downside is libraries not supporting the full set of platforms you’re targeting. Platform specific bugs will also be a problem. The risk of this increases as more platforms are added. There is already unofficial support for Flutter on Linux, Mac OS X and Windows. Library development that touches OS specifics will require an ever increasing skillset. Hopefully most of that, if not all, will be contained and isolated in the Flutter SDK.


The potential for Flutter is huge; the ability to write an app once and run it natively anywhere is a big drawcard. It also sounds like Java in the 90s; write once, debug everywhere remains true.

Flutter’s community is growing, and with it the 3rd party libraries that make development faster and easier.

As For Me?

I’ve written a small, test app, and am planning on re-writing and extending a larger app. Read about it here.