BLoC - An architecture based on Stream!

Basics of BLoC

Transcript

1. BLoC An architecture based on Stream!
2. Let’s revise the State Management - What’s the problem with setState? - Why we need of MobX (Or any other architecture)?
3. What is an architecture?, Why we need it?
4. What is an architecture? - Structure which defines relation between components. - Blueprint which will be followed by everyone in the team.
5. Why we need an architecture? - Mo make a software scalable - To maintain a standards - To make code more testable - To be on same page with all team members
6. What is BLoC? - Business Logic Components. - It’s library to separate business logic from components and make code maintainable.
7. Three layers of BLoC - Presentation / UI / View - Business logic - Data
8. BLoC
9. Why we should use BLoC? - Makes code scalable - Multiple developers can work on same code base with same pattern - Makes code more testable
10. Basics of BLoC - Stream - Sink - BLoC - Cubit
11. Stream and Sink
12. BLoC
13. Cubit
14. Components of BLoC - BlocProvider - BlocBuilder - BlocListner - BlocConsumer - MultiProvider - MultiBlocListener
15. BlocProvider
16. BlocBuilder - We can compare it with Observer of MobX. - It rebuilds UI when state of BloC or Cubit updates
17. Let’s see the Cubit and BLoC in Action!
18. BlocListner - Listens a stream and performs a actions like - Navigation, show snackbar etc
19. BlocConsumer - BlocConsumer is a combination of BlocBilder and BlocListner
20. MultiProvider - Can provide multiple instance of BloC or Cubit in application.
21. MultiBlocListener - Listens for multiple BloC or Cubit for events
22. BLoC vs MobX - Works on Stream - Need to write code and handle everything . - Bit complex to understand - It has every components for almost every use case - It has wide adaptation and heavily used. - Works on Observables - Code generator helps to reduce boilerplate code - Easy to understand - It has only three components for managing UI. - MobX is emerging
23. Thank You