-
Notifications
You must be signed in to change notification settings - Fork 37
200 Architecting a Flutter App
Fasust edited this page Oct 5, 2019
·
30 revisions
Page Table of Contents
- Vanilla, Redux, Bloc, Provide/Scoped Model
- Which one will I focus on and Why?
- Google went bach and forth on this as well.
- Why this one?
- Origin
- UI only publishes and subscribes
- Build Interface code how you want it to look like -> then make it work
-
4 Rules for BLoCs
- Only Sinks In & Streams out
- Dependencies Injectable
- No Platform Branching
- Implementation can be whatever you want
-
4 Rules for UI Classes
- “Complex Enough” views have a BLoC
- Components do not format the inputs they send to the BLoC
- Output are formated as little as possible
- If you do have Platform Branching, It should be dependent on a single BLoC bool output
Figure XXX: Bloc Architecture
Figure XXX: Bloc Architecture with Layers
Figure XXX: Wisgen Bloc Architecture
Figure XXX: Wisgen Bloc Architecture Dataflow
This Guide is licensed under the Creative Commons License (Attribution-NoDerivatives 4.0 International)
Author: Sebastian Faust.