FLUTTER ECOSYSTEM

aleksanderwozniak/deer

Minimalist Flutter Todo App, built using BLoC pattern

Deer project cover
Stars
459
Forks
103
Last push (UTC)
Nov 11, 2020
Project status
Active
Aleksander Woźniak GitHub avatar
GITHUB User

Aleksander Woźniak ↗

Flutter and Kotlin enthusiast

LanguagesDartKotlinObjective-C

Technical topics

Related packages and examples

Dependencies used

Dependency list 19 items

App categories

Rankings

Original README

English project snapshot. Visit GitHub for the latest content.

Expand / collapse project README

Deer

https://github.com/aleksanderwozniak/deer/blob/master/assets/images/4.0x/deer_logo.png

Minimalist Todo Planner app built around the idea of efficiency and clean aesthetic.

Showcase

https://github.com/aleksanderwozniak/deer/blob/assets/deer.gif https://github.com/aleksanderwozniak/deer/blob/assets/indi_list.png https://github.com/aleksanderwozniak/deer/blob/assets/gold_shp_edt.png https://github.com/aleksanderwozniak/deer/blob/assets/mint_wrk_det.png

Development

Deer uses BLoC (Business Logic Component) pattern to manage app state. If you want to use Streams in your Flutter project, then I think this is the way to go. BLoC plays exceptionally well with Flutter's reactive nature, especially since Flutter has built-in StreamBuilder widget.

Each screen is splitted into 4 files:

  • actions
  • bloc
  • screen (UI itself)
  • state

Instead of calling setState() in screen file, an action is pushed to bloc's input Stream<Action>. Then, bloc resolves that action and updates the output Stream<State>. Every state update is listened to inside screen with StreamBuilder, which updates the UI when needed. This way we achieve clear separation of concerns.

Usually with BLoC, Sink is used for input Stream, and BehaviorSubject for output Stream.

Check those resources for more details on the pattern:

  • https://youtu.be/PLHln7wHgPE
  • https://youtu.be/RS36gBEp8OI
Using built_value
flutter packages pub run build_runner build --delete-conflicting-outputs