

GetX is a natural evolution of this, not only separating the business logic but the presentation logic. In addition to making maintenance easy, this makes the sharing of modules something that until then in Flutter was unthinkable, something totally possible.īLoC was a starting point for organizing code in Flutter, it separates business logic from visualization. With GetX you know where to find each feature of your application, having clean code by default. For this, GetX uses its own dependency injection feature, decoupling the DI from its view completely. You do not need to inject your Controllers/Models/Blocs classes into your widget tree through MultiProviders. You don't need context to access your controllers/blocs through an inheritedWidget, so you completely decouple your presentation logic and business logic from your visualization layer.

You do not need context to navigate between routes, so you are not dependent on the widget tree (visualization) for this. ORGANIZATION: GetX allows the total decoupling of the View, presentation logic, business logic, dependency injection, and navigation. Dependency loading is also lazy by default. That way, in addition to saving time, you are less at risk of having unnecessary dependencies on memory. If you want to keep it in memory, you must explicitly declare "permanent: true" in your dependency. With GetX this is not necessary because resources are removed from memory when they are not used by default. Generally, the developer should be concerned with removing controllers from memory. It will save hours of development and will provide the maximum performance your application can deliver. No matter what you want to do, there is always an easier way with GetX. PRODUCTIVITY: GetX uses an easy and pleasant syntax. GetX does not use Streams or ChangeNotifier. PERFORMANCE: GetX is focused on performance and minimum consumption of resources.

This means that these are the priority for all resources in the library: PRODUCTIVITY, PERFORMANCE AND ORGANIZATION. It combines high-performance state management, intelligent dependency injection, and route management quickly and practically. GetX is an extra-light and powerful solution for Flutter. Optional Global Settings and Manual configurations.More details about dependency management.
