Start here
Your plan: 4 weeks
| Week | Days | Module |
|---|---|---|
| 1 | 1-3 | Dart 3 in depth |
| 1 | 4-5 | How Flutter really draws: three trees, constraints, keys |
| 2 | 6-8 | State management, compared honestly |
| 2 | 9-10 | Architecture and testing that interviewers respect |
| 3 | 11-13 | Performance: jank, rebuilds, isolates, DevTools |
| 3 | 14-15 | Navigation, deep links, theming, localization and RTL |
| 3-4 | 16-18 | Talking to the platform: channels, Pigeon, FFI, WebViews |
| 4 | 19-21 | Release engineering and CI |
| 4 | 22-28 | Interview revision: question bank, live coding, mobile system design |
About 1 to 1.5 hours on weekdays; use weekends for the practical tasks. This course assumes you've built Flutter apps before. It doesn't repeat the basics or the step-by-step clean architecture build (see the library's "Flutter TDD and Clean Architecture" course for that): it goes deeper and keeps asking "how would I explain this in an interview?".
Real examples come from inPace's Android app (mobile/lib/main.dart): a Flutter shell that runs a Python server with
serious_python, shows it in a WebView, and bridges notifications, files and sharing through a JavaScript channel.