Flutter Navigation Bar: A Better Way | Lifting State | 2024

[@AdrianNaranjo-i9t]

Thanks! Great video. Solved the exact problem I was having. Lifting state is definitely a little hard to grasp, but the video made sense after watching it a second time.

[@flutter_craft]

It is tricky at first, but the added flexibility is well worth it.

[@Aleinux]

Awesom. The explanation was very clear and easy to understand.

[@flutter_craft]

Glad it was helpful!

[@BeginnersCoding65]

please make more videos like this...

[@chjc0apr0]

Im plaining create a app using riverpod, should I switch it to lifting state ? Or could you make a video to compare the difference between riverpod, bloc, provider and lifting state ? Thanks for your helpful video.

[@muhammadfajrirasid6964]

I think using this approach will mean that the animations on selected destination icon (e.g. background color change) will not work.

[@hussamelfikky1351]

why do i have to repeat CustomNavigationBar in every screen ? i didn't get it

[@flutter_craft]

Using a single scaffold means you can’t set a different title or action button for each screen (see 8:00 in video) unless you nest scaffolds or shove code in the wrong places. By setting a scaffold for each screen and then calling the CustomNavigationBar widget from each nav screen can be customized.

[@flagger1]

This method seems inefficient, couldn't you have just created appbars in each of the different screen's scaffold?? In that way they change and you'd still have to use one Bottom Nav

[@flutter_craft]

Hi @flagger1, If I'm understanding your question correctly, this method is doing what you're asking: By creating a scaffold for each nav screen, you're able to create an appbar for each different screen. The nav bar is also part of the scaffold, but we don't want to repeat the code three times (inefficient, difficult to maintain), so we extract that into a custom widget.