Flutter Engineering, Architectural path
summary
Argues that architecture reduces costly rework by shifting decisions early, outlines four pillars and shows concrete patterns: layered architecture (presentation/domain/data) with clear contracts, an event/stream-driven architecture using broadcasts and multiple subscribers, and a plugin-based route registration demo that registers routes at runtime so features load independently. Presents a working demo and a full implementation example, notes trade-offs—runtime modularity increases complexity and maintenance cost—and points to a companion repo and book for code and patterns.
AI-written summary · about
chapters (10)
- 0:00Flutter engineering intro
- 3:40Why architecture matters
- 8:15Separation of concerns
- 10:54Choosing frameworks
- 13:13Layer architecture
- 22:33Event-driven architecture
- 27:05Pluggable features
- 36:03Iterative architecture
- 38:30Complexity vs maintainability
- 40:22Resources and closing
related talks
18mSoftware Architecture Building Better Applications with Architecture Best Practices
42mStratified design and functional architecture
50mTowards an Evolutionary Architecture
24mBuilding Software Architecture from First Principles
30mThe Art of Front-end Architecture
34mScalable Angular Architecture
24mBuilding Software Architecture from First Principles
29mIntentional Architecture in Agile Organizations