#BLoC

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.

Don't make one single BLoC for the whole page. Follow the Single Responsibility Principle and split UI components into small features with their own BLoCs.

Sometimes your BLoC looks fine, but part of its logic lives outside the state hidden in private fields that never get emitted. That's ghost state. In this post, I show a real example of how it happens, and how to fix it so your state tells the whole story.

(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.