Should We Flutter?
summary
Quiz-driven evaluation of Flutter that reports concrete tradeoffs: apps are written in Dart and compiled to native and rendered with Skia, enabling hot reload and smooth 60fps UI; shipping bundles currently adds ~7 MB and lacks Android dynamic delivery or instant modularization; missing partial-screen Google Maps/webview pushes teams to use full-screen native activities (Hamilton uses this for camera), introducing a risk of supporting a third platform via platform channels; best fit for brand-driven or material UIs and teams willing to adopt a new language and fix plugin gaps.
AI-written summary · about
chapters (10)
- 0:00Introduction to Flutter
- 3:58Quiz setup and first question
- 8:15Flutter architecture and rendering
- 12:33Feature completeness in Flutter
- 15:42Platform services and plugins
- 19:17OS integration and app size
- 23:15Developer experience with Flutter
- 27:30Team background and Dart language
- 28:54Time and flexibility for adoption
- 30:58Summary and resources
related talks
49mWhat's Awesome about Flutter
50mTake off with Flutter
41mWhy is Flutter the mobile SDK developers deserve...
24mKeynote: Flutter
40mHow I met Flutter
45mFlutter: A journey of productivity and happiness
32m"Flutter: How we're building a UI framework for tomorrow at Google"
47mFlutter - how to make a beautiful app in an hour?