Flutter Architecture Components
summary
Presents a concrete, Flutter 2.5–based MVC using Riverpod+ChangeNotifier and a service locator for dependency injection, with controllers as ChangeNotifiers, repositories orchestrating local+remote data sources, and immutable UI-state objects. Demonstrates a working Pokemon app (uses the public API with ~141 entries), adds a new Pokemon on refresh, uses a 3s artificial delay and shows background-safe updates and cached details, arguing this yields simple, scalable reactive caching, unidirectional data flow, and single source of truth.
AI-written summary · about
chapters (11)
- 0:00Introduction to architecture
- 5:55Demo app overview
- 9:46State Management basics
- 12:57Simple State Management
- 16:48What is architecture?
- 20:23Code structure principles
- 23:14Three-layer architecture
- 27:07UI State management
- 32:32Unidirectional data flow
- 37:51Domain layer benefits
- 38:56Choosing the right architecture
related talks
34mModular Flutter App Architecture Answering the What, When and How
37mBuilding scalable, maintainable and robust apps in Flutter
39mRefactoring Plaid App – A reactive MVP approach
38mArchitecture Agnostic UI Development
30mCat-like Development: Flutter for Efficiency
37mFlutter: Mobile Development for Busy People
22mFlutter State Smackdown: Comparing BLoC, Provider, Riverpod
22mClean Architecture in Flutter for Maintainable Code