Recently, there is a lot of mobile developers migrating to Flutter and some of them, always get in the wrong direction in terms of selecting a pattern for state management. When it comes to Clean architecture and good maintainability, get is not a choice.
Do not get me wrong, but, one of the main reasons people love getX is because is easy to use, but painful to remove in the future. One of the principles to use Clean architecture in your projects is to easily switch between packages and patterns.
This is one of the main reasons some companies that chose getX as their main state manager, get frustrated with flutter, when they try to add things outside getX, they have difficulty or give up trying it. So, if one day you decide to come to flutter, do not try getX.
Top comments (0)