Reactive Architecture for Flutter
summary
Explains when ScopedModel becomes a maintenance problem and why BLoC with streams scales better: concrete code shows a counter using ScopedModel rebuilds many widgets versus a BLoC using a broadcast StreamController, sink and StreamBuilder that updates only wrapped widgets. Demonstrates a BlocProvider that supplies a single block instance across children, mentions optional RxDart, warns to close streams to avoid leaks, and shows a working “WhatToDo” task app using multiple blocks.
AI-written summary · about
chapters (15)
- 0:00Introduction to talk
- 0:45What is software architecture
- 3:10Understanding reactive programming
- 4:53Scope Model explained
- 8:05Scope Model demo with counter
- 13:34Limitations of Scope Model
- 16:24Introducing BLoC pattern
- 18:09BLoC implementation with streams
- 22:04BLoC demo with counter
- 24:21BLoC Provider for state sharing
- 27:10BLoC Provider implementation
- 28:36Real-world app example
- 32:13Resources and references
- 32:34Speaker's journey and advice
- 34:51Q&A session begins
related talks
46mHow to Cook Flutter Properly- 46mHow to Cook Flutter Correctly
21mBuild a reactive Flutter App
34mBuild reactive mobile apps with Flutter
44mState Management in Flutter
37mBuilding scalable, maintainable and robust apps in Flutter
45mArchitectural Thinking on Flutter State Management
22mFlutter State Smackdown: Comparing BLoC, Provider, Riverpod