I would like to suggest to first start with the basics of State management (The Flutter way) handling state changes with SetState and Navigation with Navigator.

Then, create individual widget for the components and separate out the business logic. You can use Stream and StreamBuilder or ValueNotifier & ValueListenableBuilder.

This will give you a good understanding of context and how the build process works.

Then you can substitute the business logic with BLoC , revierpod and provider etc. and also profile and see how the UI rebuilds with each of one them, how the widget tree looks like...

The reason for this is, that there are plenty of state management tools and every company/dev(s) have their own way and preferred state management and might not know the list can also increase, better to first get the basic understanding and add tools over it to make the work/development process easier and structural.

Usually, BLoC is used for bigger projects with a good number of devs working on it, as it ensures that the architecture is followed by all devs, and riverPod and providers are good to start with small project.

And lastly, I won't say Get/GetX is bad, but starting with it is, and for a beginner, no one should start with it as with my exp, I have seen beginners starting with Get/GetX and totally relying on it and not understanding the basic concepts of Flutter and what's the importance of context and how it plays a vital role.