After nine months hacking on Flutter from alpha to beta to release candidate, the way I write Flutter apps has morphed and mutated. How I coded Flutter apps a few months ago is pretty different to how I code them now, and will almost certainly continue to evolve.
Here’s a few mistakes made, a few lessons learned, and a few habits I’ve formed some may think good, and others … maybe not so much.
This will be a lighthearted romp through all things Flutter.
YOU MAY ALSO LIKE:
- Lightbend Akka for Scala - Expert (in London on 26th - 27th November 2018)
- Brian Egan's Flutter and Dart Workshop (in London on 19th - 20th March 2019)
- iOSCon 2019 - The conference for iOS and Swift Developers (in London on 21st - 22nd March 2019)
- Fast Track to Android Architecture (in London on 25th - 27th March 2019)
Lessons Learned from Writing Flutter Apps
Matt leads developer relations for Flutter from Google’s Mountain View campus. He recently joined the Flutter team, having spent three years working on Android and Wear. He’s a bit of a language geek, and is thoroughly enjoying adding Dart to the portfolio of languages to write cool thing in. When he’s not hacking on Flutter, you’ll probably find him in the gym wearing far too many fitness sensors.