Flutter provides a lot of flexibility in deciding how to organize and architect your apps. While this freedom is very valuable, it can also lead to apps with large classes, inconsistent naming schemes, as well as mismatching or missing architectures. These types of issues can make testing, maintaining and extending your apps difficult.
The Flutter Architecture Samples project demonstrates strategies to help solve or avoid these common problems. This project implements the same "Todos" app using different architectural concepts and tools.
Samples
- Vanilla Lifting State Up Web Demo
- InheritedWidget Web Demo
- ChangeNotifier + Provider Web Demo
- BLoC Web Demo
- Bloc Library Web Demo
- Mobx Web Demo
- Redux Web Demo
- "Simple" BLoC Example Web Demo
- MVI Web Demo
- states_rebuilder Web Demo
- built_redux
- scoped_model
- Redux and Firestore
- MVU
- MVC Example
- Frideos library
Supporting code
Contributors
© 2017 Brian Egan and contributors.