Hey there! I'm a Flutter Developer, and I'd like to make some suggestions for the Roadmap, which I really liked.
In this part, Storage, I suggest the inclusion of Hasura, which is another type of backend/db, like Firebase, used by some devs. But in the job market, as far as I know, it's not used much. So it's just one more option.
Also in Storage, something that is very much used by flutter devs, and that is very important to learn, are the Firebase Cloud Functions. Many APIs we use need to be consumed through them, so they are very important.
Other Firebase features that are used a lot, but aren't really necessary to learn in the beginning, are Flutter Fire (for quick integration with Flutter) and Firebase Hosting.
In this part of Widgets, I suggest adding the InheritedWidget, as an option, which is the native base of many Widgets. Learning this helps to understand how some flutter widgets work.
Here I strongly suggest adding a container for project architectures, to display the most used ones:
MVC (very important)
MVVM
Clean Architecture (important but advanced)
In this section of State Management, I suggest uniting the two containers referring to BLoc, removing the importance of Velocity X and Get X (they are not very used) and adding the following managers:
ValueNotifier and ChangeNotifier, which are native, so it's used a lot in some situations and is highly recommended. And they are reactive.
MobX. It is a very used state management package, mainly together with Modular. It is reactive too and easy to use.
I also recommend linking the Reactive Programming container with the State Management container, as one leads to the other. Many state managers are also reactive.
Ah, I also suggest adding study sections for Flutter Web, Desktop, and Mobile.
And those are my suggestions. I hope it helps in some way.
Hey there! I'm a Flutter Developer, and I'd like to make some suggestions for the Roadmap, which I really liked.
In this part, Storage, I suggest the inclusion of Hasura, which is another type of backend/db, like Firebase, used by some devs. But in the job market, as far as I know, it's not used much. So it's just one more option.
Also in Storage, something that is very much used by flutter devs, and that is very important to learn, are the Firebase Cloud Functions. Many APIs we use need to be consumed through them, so they are very important.
Other Firebase features that are used a lot, but aren't really necessary to learn in the beginning, are Flutter Fire (for quick integration with Flutter) and Firebase Hosting.
In this part of Widgets, I suggest adding the InheritedWidget, as an option, which is the native base of many Widgets. Learning this helps to understand how some flutter widgets work.
Here I strongly suggest adding a container for project architectures, to display the most used ones: MVC (very important) MVVM Clean Architecture (important but advanced)
In this section of State Management, I suggest uniting the two containers referring to BLoc, removing the importance of Velocity X and Get X (they are not very used) and adding the following managers: ValueNotifier and ChangeNotifier, which are native, so it's used a lot in some situations and is highly recommended. And they are reactive. MobX. It is a very used state management package, mainly together with Modular. It is reactive too and easy to use.
I also recommend linking the Reactive Programming container with the State Management container, as one leads to the other. Many state managers are also reactive.
Ah, I also suggest adding study sections for Flutter Web, Desktop, and Mobile.
And those are my suggestions. I hope it helps in some way.