#Architecture

Many people think that creating an abstract class, an implementation and injecting the abstraction is already applying the Dependency Inversion Principle. It's not. This post walks through the questions I keep hearing about Clean, layered and DIP, and pins down the one detail that makes the difference.

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.

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

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