Initially, the Business Logic Component (BLoC) pattern was introduced by Google as a solution to handle states in Flutter applications. It allows you to reduce the workload on UI components by separating the business logic from them.
The concept behind the BLoC pattern is straightforward. As you can see in the above figure, business logic will be separated from UI components. First, they will send events to the BLoC using an observer. And then, after processing the request, UI components will be notified by the BLoC using observables.
When the business logic is standalone from UI components, the impact on the application will be minimum. You will be able to change the business logic any time you want without affecting the UI components.
Since the business logic is in one place, UI components can reuse logic without duplicating the code so that the simplicity of the app will increase.
When writing test cases, developers can focus on the BLoC itself. So the code base is not going to be messed up.
Over time, application requirements may change, and business logic can keep growing. In such situations, developers can even create multiple BLoCs to maintain the clarity of the codebase.
Moreover, BLoC patterns are platform and environment independent so that developers can use the same BLoC pattern in many projects.
Now, let’s implement the BLoC class. The BLoC class will be responsible for implementing all subjects related to business logic. In this example, it is responsible for the counter logic.
So, I have created a file named
CounterBloc.js inside the bloc directory and used a pipe to pass the counter to the UI components.
There is simple logic in this class. However, when an app grows in size, imagine the complexity if we do not separate the business logic.
In this step, I will create the
StreamBuilder.js inside the utils directory to handle the counter request from the UI. Moreover, developers can handle errors and implement customer handlers within this.
AsyncSnapshot class, we can initialize a constructor, handle our data (check availability, etc. ), and handle errors. But in this example, I have only returned the data for ease of demonstration.
The initial data is passed into
AysncSnapshot class and stored in the snapshot state for each subscription. Then it will get rendered in the UI components.
As you can see now,
decrease() methods are called directly within the UI component. However, output data is handle by a stream builder.
It is better to have an intermediate layer to implement custom handlers to handle errors.
app.js file, the BLoC is initialized using the
CounterBloc class. Thus, the
Counter component is used by passing the BLoC as a prop.
That’s it. Now you can treat your business logic as a separate entity outside your UI components and change it as you need.
❤️ Brainstash Inc.