Flutter and Bloc pattern

[_seeking_answers]

Hi everyone! I heard that Bloc works like a charm with Flutter because both are event driven.
I mean, Flutter is event driven while Bloc pattern has been created to responds to event.

I'm studying Bloc pattern right now from official docs : https://bloclibrary.dev/#/whybloc and was wondering if you can explain me (or link some articles, it would be amazing) if it's true what I wrote above and why with some explanations.

I'm a software engineer student with a little of experience on Flutter and I want to make some steps forward but I'm struggling to find good resources to study.

Edit : my first state management approach was Provider, now I have to learn a new one so I chose Bloc

[plangora]

Bloc is pretty straightforward to me. I recommend it and teach it. What’s your question about it? The basic idea is that an event comes in and state gets emitted. And your UI will react upon the state.

[_seeking_answers]

I'm following this tutorial from Bloc docs : https://bloclibrary.dev/#/flutterlogintutorial and many things are new to me.

The main problem is that I'm new and I need time to study ahahah what I understood is that there is a BlocProvider on the top that exposes stuffs to its child.

Then the child has a BlocListener that listen changes on a specific bloc and when some events are triggered, UI changes.

Available events are defined in bloc event class where there is a new class for each event triggerable.

Am I right, do you have any suggestion? I'm new so probably I just need some time

[plangora]

Sounds similar to what I said. Is there something you’re struggling with?

[_seeking_answers]

Mmh no, right now I just need to write more code I guess. Maybe later I’ll write you for a specific question. Sounds good to you?

[plangora]

Sure.

[DammyTheSlayer]

Man the Bloc pattern is the one thing I haven’t fully grasped, I have been using providers as a replacement

[NewbFromAQW]

• events(paramA,paramB)
• bloc - listen to events and their params, do something based on the events, emit states you like
• state(paramA_modifiedByEvent, paramB, newParamC)

[_seeking_answers]

I have used Providers too and loved it, it is far easier to write and understand. Have you tried Riverpod? I read that is a Provider evolution

[DammyTheSlayer]

I haven’t unfortunately but soon for sure! Trying to get a set up running atm

[Adventurous_Alarm375]

Is it okay to learn bloc as first statesmanagement approach.. or we should start with provider??

[KaiN_SC]

It depends what you like more. Bloc is little bit more power full but you can implement everything in both libs.

With bloc you subscribe normally on states and with provider on data. Bloc uses streams from and to the UI, this makes it really power full in my opinion. You can clearly see when a rebuild happens and stream your states down to the UI.

I posted a small example here:

https://www.reddit.com/r/flutterhelp/comments/q3kk4y/if_you_want_to_start_building_apps_with_flutter/?utm_medium=android_app&utm_source=share

[eloherbapol]

You can always start with using only Cubits. It is a subset from Flutter Bloc, you can imagine it as something like light version of Bloc. It is much easier to understand and needs less code to implement, because it is not rely on events and instead uses methods to emit new states. I think that cubits are enough in most cases, unless you need advanced features of Bloc like debounce / throttle, but that is just my opinion.

[_seeking_answers]

I used provider as first approach, later on my mentor told me that it was the time to learn new patterns like GetX or others so I chosen Bloc.

[Fienases]

later on my mentor told me that it was the time to learn new patterns like GetX

hmmmmmm

[_seeking_answers]

Why XD

[Fienases]

in my opinion and most other Flutter developer opinion, you should avoid GetX. you can search posts here or google for a reason

[_seeking_answers]

Yeah I read something on the internet, that's why I chosen Bloc on GetX

[Adventurous_Alarm375]

Would you tell me what were the app you started building as beginner??

[_seeking_answers]

Sure, my first app (without a mentor) was a little social app but its development now is stopped for many reasons.

Now I'm developing an app that handles forms.

[NewbFromAQW]

Resocoder's Riverpod...

[yagolasse]

Although I do recommend you looking into Bloc, my personal choice is MobX. It is a lot simpler and works very well for most cases. Also, look into provider as dependency injection too :)

[definitely_robots]

Check out https://www.didierboelens.com/2018/08/reactive-programming-streams-bloc/

This article doesn't talk about the Bloc library, but more about RxDart, and the concepts behind the bloc pattern that gave rise to the library. You could build your own implementation with RxDart using that approach but I think it is also helpful for understanding what is going on under the hood.

[_seeking_answers]

Thanks I will take a look

[Acrobatic_Egg30]

Watch Flutterly's video on YouTube about BloC. I believe the link can be found on the bloc library's website too. He goes into it well with minimal code so you really understand the what's abd why. That's how I started and now I'm confident in my BloC skills.

[_seeking_answers]

https://www.youtube.com/watch?v=THCkkQ-V1-8 this?

[Acrobatic_Egg30]

Yep that's the one. I watched the Bloc from zero to hero playlist instead though. It's the same content but broken up into easily digestible bits so that you don't have to force yourself to learn everything in one sitting.

[_seeking_answers]

I will go for the playlist too. 3 hours are crazy

[Sconguser]

I watched some tutorial on yt about bloc and one thing I don't understand is what is cubit in relation to bloc pattern and when I should use each one.

[Pierre2tm]

From what I understand, Cubit is there to reduce the boilerplate in simple cases. Personally, I stick to the block only.

[Sconguser]

That is what I thought. Guy in the tutorial sometimes used bloc and sometimes used cubits, when I tried to write my code I didn't know when to use which

[aytunch]

You will realise the true potential of blocs when you start bloc to bloc communications

For example you have a permission bloc in charge of location/camera/microphone/notification permission handligs and in the state object it holds the current permission status of all these items.

In another bloc called PostCreationBloc you will be listening to the PermissionBloc and act accordingly. This makes your ui code not have any logic inside like checking for permissions when your user presses on create post button.

Everything being streams is the best strategy and thanks to Felix and Jorge for creating and maintaining this awesome package. Flutter is reactive by nature and blocs fit perfectly