Don’t make one single bloc for the home page, it will bloat the app state if it needs a lot of information. Follow the Single Responsibility Principle and split the UI components into small presentation layer features with their own BLoCs.
One reactive source of truth. The repository streams data, and each feature listens and derives its own state independently. Clean, decoupled, and easy to scale.
Read More(and how the Mediator Pattern can save you) Sometimes in a Flutter app, one BLoC starts depending on another. Maybe the profile screen needs the current user ID from the AuthBloc. So we inject one BLoC into the other. It works. Until it doesn't.
Read MoreProp drilling happens when data travels through widgets that do not need it. In this post I show how I removed it in my project and made the code cleaner using a provider.
Read More