[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9097":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":37,"readmeContent":38,"aiSummary":39,"trendingCount":16,"starSnapshotCount":16,"syncStatus":40,"lastSyncTime":41,"discoverSource":42},9097,"getx","jonataslaw\u002Fgetx","jonataslaw","Open screens\u002Fsnackbars\u002Fdialogs\u002FbottomSheets without context, manage states and inject dependencies easily with Get.","",null,"Dart",11181,1846,124,1068,0,3,17,1,44.8,"MIT License",false,"master",true,[26,27,28,29,30,5,31,32,33,34,35,36],"dart","dependency-injection","flutter","framework","get","http","internationalization","mobile","routes","state-management","web","2026-06-12 02:02:02","![](https:\u002F\u002Fraw.githubusercontent.com\u002Fjonataslaw\u002Fgetx-community\u002Fmaster\u002Fget.png)\n\n[![pub package](https:\u002F\u002Fimg.shields.io\u002Fpub\u002Fv\u002Fget.svg?label=get&color=blue)](https:\u002F\u002Fpub.dev\u002Fpackages\u002Fget)\n[![popularity](https:\u002F\u002Fimg.shields.io\u002Fpub\u002Fpopularity\u002Fget?logo=dart)](https:\u002F\u002Fpub.dev\u002Fpackages\u002Fget\u002Fscore)\n[![likes](https:\u002F\u002Fimg.shields.io\u002Fpub\u002Flikes\u002Fget?logo=dart)](https:\u002F\u002Fpub.dev\u002Fpackages\u002Fget\u002Fscore)\n[![pub points](https:\u002F\u002Fimg.shields.io\u002Fpub\u002Fpoints\u002Fsentry?logo=dart)](https:\u002F\u002Fpub.dev\u002Fpackages\u002Fget\u002Fscore)\n![building](https:\u002F\u002Fgithub.com\u002Fjonataslaw\u002Fget\u002Fworkflows\u002Fbuild\u002Fbadge.svg)\n[![style: effective dart](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fstyle-effective_dart-40c4ff.svg)](https:\u002F\u002Fpub.dev\u002Fpackages\u002Feffective_dart)\n[![Discord Shield](https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F722900883784073290.svg?logo=discord)](https:\u002F\u002Fdiscord.com\u002Finvite\u002F9Hpt99N)\n[![Get on Slack](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fslack-join-orange.svg)](https:\u002F\u002Fcommunityinviter.com\u002Fapps\u002Fgetxworkspace\u002Fgetx)\n[![Telegram](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fchat-on%20Telegram-blue.svg)](https:\u002F\u002Ft.me\u002Fjoinchat\u002FPhdbJRmsZNpAqSLJL6bH7g)\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FSolido\u002Fawesome-flutter\">\n\u003Cimg alt=\"Awesome Flutter\" src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FAwesome-Flutter-blue.svg?longCache=true&style=flat-square\" \u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fwww.buymeacoffee.com\u002Fjonataslaw\" target=\"_blank\">\u003Cimg src=\"https:\u002F\u002Fi.imgur.com\u002FaV6DDA7.png\" alt=\"Buy Me A Coffee\" style=\"height: 41px !important;width: 174px !important; box-shadow: 0px 3px 2px 0px rgba(190, 190, 190, 0.5) !important;-webkit-box-shadow: 0px 3px 2px 0px rgba(190, 190, 190, 0.5) !important;\" > \u003C\u002Fa>\n\n![](https:\u002F\u002Fraw.githubusercontent.com\u002Fjonataslaw\u002Fgetx-community\u002Fmaster\u002Fgetx.png)\n\n\u003Cdiv align=\"center\">\n\n**Languages:**\n\n[![English](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-English-blueviolet?style=for-the-badge)](README.md)\n[![Vietnamese](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Vietnamese-blueviolet?style=for-the-badge)](README-vi.md)\n[![Indonesian](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Indonesian-blueviolet?style=for-the-badge)](README.id-ID.md)\n[![Urdu](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Urdu-blueviolet?style=for-the-badge)](README.ur-PK.md)\n[![Chinese](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Chinese-blueviolet?style=for-the-badge)](README.zh-cn.md)\n[![Portuguese](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Portuguese-blueviolet?style=for-the-badge)](README.pt-br.md)\n[![Spanish](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Spanish-blueviolet?style=for-the-badge)](README-es.md)\n[![Russian](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Russian-blueviolet?style=for-the-badge)](README.ru.md)\n[![Polish](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Polish-blueviolet?style=for-the-badge)](README.pl.md)\n[![Korean](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Korean-blueviolet?style=for-the-badge)](README.ko-kr.md)\n[![French](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-French-blueviolet?style=for-the-badge)](README-fr.md)\n[![Japanese](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Japanese-blueviolet?style=for-the-badge)](README.ja-JP.md)\n[![Hindi](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Hindi-blueviolet?style=for-the-badge)](README-hi.md)\n[![Bangla](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Bangla-blueviolet?style=for-the-badge)](README-bn.md)\n[![Nepali](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLanguage-Nepali-blueviolet?style=for-the-badge)](README-ne.md)\n\n\u003C\u002Fdiv>\n\n- [About Get](#about-get)\n- [Installing](#installing)\n- [Counter App with GetX](#counter-app-with-getx)\n- [The Three pillars](#the-three-pillars)\n  - [State management](#state-management)\n    - [Reactive State Manager](#reactive-state-manager)\n    - [More details about state management](#more-details-about-state-management)\n  - [Route management](#route-management)\n    - [More details about route management](#more-details-about-route-management)\n  - [Dependency management](#dependency-management)\n    - [More details about dependency management](#more-details-about-dependency-management)\n- [Utils](#utils)\n  - [Internationalization](#internationalization)\n    - [Translations](#translations)\n      - [Using translations](#using-translations)\n    - [Locales](#locales)\n      - [Change locale](#change-locale)\n      - [System locale](#system-locale)\n  - [Change Theme](#change-theme)\n  - [GetConnect](#getconnect)\n    - [Default configuration](#default-configuration)\n    - [Custom configuration](#custom-configuration)\n  - [GetPage Middleware](#getpage-middleware)\n    - [Priority](#priority)\n    - [Redirect](#redirect)\n    - [onPageCalled](#onpagecalled)\n    - [OnBindingsStart](#onbindingsstart)\n    - [OnPageBuildStart](#onpagebuildstart)\n    - [OnPageBuilt](#onpagebuilt)\n    - [OnPageDispose](#onpagedispose)\n  - [Other Advanced APIs](#other-advanced-apis)\n    - [Optional Global Settings and Manual configurations](#optional-global-settings-and-manual-configurations)\n    - [Local State Widgets](#local-state-widgets)\n      - [ValueBuilder](#valuebuilder)\n      - [ObxValue](#obxvalue)\n  - [Useful tips](#useful-tips)\n    - [GetView](#getview)\n    - [GetResponsiveView](#getresponsiveview)\n      - [How to use it](#how-to-use-it)\n    - [GetWidget](#getwidget)\n    - [GetxService](#getxservice)\n- [Breaking changes from 2.0](#breaking-changes-from-20)\n- [Why Getx?](#why-getx)\n- [Community](#community)\n  - [Community channels](#community-channels)\n  - [How to contribute](#how-to-contribute)\n  - [Articles and videos](#articles-and-videos)\n\n# About Get\n\n- GetX is an extra-light and powerful solution for Flutter. It combines high-performance state management, intelligent dependency injection, and route management quickly and practically.\n\n- GetX has 3 basic principles. This means that these are the priority for all resources in the library: **PRODUCTIVITY, PERFORMANCE AND ORGANIZATION.**\n  - **PERFORMANCE:** GetX is focused on performance and minimum consumption of resources. GetX does not use Streams or ChangeNotifier.\n\n  - **PRODUCTIVITY:** GetX uses an easy and pleasant syntax. No matter what you want to do, there is always an easier way with GetX. It will save hours of development and will provide the maximum performance your application can deliver.\n\n    Generally, the developer should be concerned with removing controllers from memory. With GetX this is not necessary because resources are removed from memory when they are not used by default. If you want to keep it in memory, you must explicitly declare \"permanent: true\" in your dependency. That way, in addition to saving time, you are less at risk of having unnecessary dependencies on memory. Dependency loading is also lazy by default.\n\n  - **ORGANIZATION:** GetX allows the total decoupling of the View, presentation logic, business logic, dependency injection, and navigation. You do not need context to navigate between routes, so you are not dependent on the widget tree (visualization) for this. You don't need context to access your controllers\u002Fblocs through an inheritedWidget, so you completely decouple your presentation logic and business logic from your visualization layer. You do not need to inject your Controllers\u002FModels\u002FBlocs classes into your widget tree through `MultiProvider`s. For this, GetX uses its own dependency injection feature, decoupling the DI from its view completely.\n\n    With GetX you know where to find each feature of your application, having clean code by default. In addition to making maintenance easy, this makes the sharing of modules something that until then in Flutter was unthinkable, something totally possible.\n    BLoC was a starting point for organizing code in Flutter, it separates business logic from visualization. GetX is a natural evolution of this, not only separating the business logic but the presentation logic. Bonus injection of dependencies and routes are also decoupled, and the data layer is out of it all. You know where everything is, and all of this in an easier way than building a hello world.\n    GetX is the easiest, practical, and scalable way to build high-performance applications with the Flutter SDK. It has a large ecosystem around it that works perfectly together, it's easy for beginners, and it's accurate for experts. It is secure, stable, up-to-date, and offers a huge range of APIs built-in that are not present in the default Flutter SDK.\n\n- GetX is not bloated. It has a multitude of features that allow you to start programming without worrying about anything, but each of these features are in separate containers and are only started after use. If you only use State Management, only State Management will be compiled. If you only use routes, nothing from the state management will be compiled.\n\n- GetX has a huge ecosystem, a large community, a large number of collaborators, and will be maintained as long as the Flutter exists. GetX too is capable of running with the same code on Android, iOS, Web, Mac, Linux, Windows, and on your server.\n  **It is possible to fully reuse your code made on the frontend on your backend with [Get Server](https:\u002F\u002Fgithub.com\u002Fjonataslaw\u002Fget_server)**.\n\n**In addition, the entire development process can be completely automated, both on the server and on the front end with [Get CLI](https:\u002F\u002Fgithub.com\u002Fjonataslaw\u002Fget_cli)**.\n\n**In addition, to further increase your productivity, we have the\n[extension to VSCode](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=get-snippets.get-snippets) and the [extension to Android Studio\u002FIntellij](https:\u002F\u002Fplugins.jetbrains.com\u002Fplugin\u002F14975-getx-snippets)**\n\n# Installing\n\nAdd Get to your pubspec.yaml file:\n\n```yaml\ndependencies:\n  get:\n```\n\nImport get in files that it will be used:\n\n```dart\nimport 'package:get\u002Fget.dart';\n```\n\n# Counter App with GetX\n\nThe \"counter\" project created by default on new project on Flutter has over 100 lines (with comments). To show the power of Get, I will demonstrate how to make a \"counter\" changing the state with each click, switching between pages and sharing the state between screens, all in an organized way, separating the business logic from the view, in ONLY 26 LINES CODE INCLUDING COMMENTS.\n\n- Step 1:\n  Add \"Get\" before your MaterialApp, turning it into GetMaterialApp\n\n```dart\nvoid main() => runApp(GetMaterialApp(home: Home()));\n```\n\n- Note: this does not modify the MaterialApp of the Flutter, GetMaterialApp is not a modified MaterialApp, it is just a pre-configured Widget, which has the default MaterialApp as a child. You can configure this manually, but it is definitely not necessary. GetMaterialApp will create routes, inject them, inject translations, inject everything you need for route navigation. If you use Get only for state management or dependency management, it is not necessary to use GetMaterialApp. GetMaterialApp is necessary for routes, snackbars, internationalization, bottomSheets, dialogs, and high-level apis related to routes and absence of context.\n- Note²: This step is only necessary if you gonna use route management (`Get.to()`, `Get.back()` and so on). If you not gonna use it then it is not necessary to do step 1\n\n- Step 2:\n  Create your business logic class and place all variables, methods and controllers inside it.\n  You can make any variable observable using a simple \".obs\".\n\n```dart\nclass Controller extends GetxController{\n  var count = 0.obs;\n  increment() => count++;\n}\n```\n\n- Step 3:\n  Create your View, use StatelessWidget and save some RAM, with Get you may no longer need to use StatefulWidget.\n\n```dart\nclass Home extends StatelessWidget {\n\n  @override\n  Widget build(context) {\n\n    \u002F\u002F Instantiate your class using Get.put() to make it available for all \"child\" routes there.\n    final Controller c = Get.put(Controller());\n\n    return Scaffold(\n      \u002F\u002F Use Obx(()=> to update Text() whenever count is changed.\n      appBar: AppBar(title: Obx(() => Text(\"Clicks: ${c.count}\"))),\n\n      \u002F\u002F Replace the 8 lines Navigator.push by a simple Get.to(). You don't need context\n      body: Center(child: ElevatedButton(\n              child: Text(\"Go to Other\"), onPressed: () => Get.to(Other()))),\n      floatingActionButton:\n          FloatingActionButton(child: Icon(Icons.add), onPressed: c.increment));\n  }\n}\n\nclass Other extends StatelessWidget {\n  \u002F\u002F You can ask Get to find a Controller that is being used by another page and redirect you to it.\n  final Controller c = Get.find();\n\n  @override\n  Widget build(context){\n     \u002F\u002F Access the updated count variable\n     return Scaffold(body: Center(child: Text(\"${c.count}\")));\n  }\n}\n```\n\nResult:\n\n![](https:\u002F\u002Fraw.githubusercontent.com\u002Fjonataslaw\u002Fgetx-community\u002Fmaster\u002Fcounter-app-gif.gif)\n\nThis is a simple project but it already makes clear how powerful Get is. As your project grows, this difference will become more significant.\n\nGet was designed to work with teams, but it makes the job of an individual developer simple.\n\nImprove your deadlines, deliver everything on time without losing performance. Get is not for everyone, but if you identified with that phrase, Get is for you!\n\n# The Three pillars\n\n## State management\n\nGet has two different state managers: the simple state manager (we'll call it GetBuilder) and the reactive state manager (GetX\u002FObx)\n\n### Reactive State Manager\n\nReactive programming can alienate many people because it is said to be complicated. GetX turns reactive programming into something quite simple:\n\n- You won't need to create StreamControllers.\n- You won't need to create a StreamBuilder for each variable\n- You will not need to create a class for each state.\n- You will not need to create a get for an initial value.\n- You will not need to use code generators\n\nReactive programming with Get is as easy as using setState.\n\nLet's imagine that you have a name variable and want that every time you change it, all widgets that use it are automatically changed.\n\nThis is your count variable:\n\n```dart\nvar name = 'Jonatas Borges';\n```\n\nTo make it observable, you just need to add \".obs\" to the end of it:\n\n```dart\nvar name = 'Jonatas Borges'.obs;\n```\n\nAnd in the UI, when you want to show that value and update the screen whenever the values changes, simply do this:\n\n```dart\nObx(() => Text(\"${controller.name}\"));\n```\n\nThat's all. It's _that_ simple.\n\n### More details about state management\n\n**See an more in-depth explanation of state management [here](.\u002Fdocumentation\u002Fen_US\u002Fstate_management.md). There you will see more examples and also the difference between the simple state manager and the reactive state manager**\n\nYou will get a good idea of GetX power.\n\n## Route management\n\nIf you are going to use routes\u002Fsnackbars\u002Fdialogs\u002Fbottomsheets without context, GetX is excellent for you too, just see it:\n\nAdd \"Get\" before your MaterialApp, turning it into GetMaterialApp\n\n```dart\nGetMaterialApp( \u002F\u002F Before: MaterialApp(\n  home: MyHome(),\n)\n```\n\nNavigate to a new screen:\n\n```dart\n\nGet.to(NextScreen());\n```\n\nNavigate to new screen with name. See more details on named routes [here](.\u002Fdocumentation\u002Fen_US\u002Froute_management.md#navigation-with-named-routes)\n\n```dart\n\nGet.toNamed('\u002Fdetails');\n```\n\nTo close snackbars, dialogs, bottomsheets, or anything you would normally close with Navigator.pop(context);\n\n```dart\nGet.back();\n```\n\nTo go to the next screen and no option to go back to the previous screen (for use in SplashScreens, login screens, etc.)\n\n```dart\nGet.off(NextScreen());\n```\n\nTo go to the next screen and cancel all previous routes (useful in shopping carts, polls, and tests)\n\n```dart\nGet.offAll(NextScreen());\n```\n\nNoticed that you didn't have to use context to do any of these things? That's one of the biggest advantages of using Get route management. With this, you can execute all these methods from within your controller class, without worries.\n\n### More details about route management\n\n**Get works with named routes and also offers lower-level control over your routes! There is in-depth documentation [here](.\u002Fdocumentation\u002Fen_US\u002Froute_management.md)**\n\n## Dependency management\n\nGet has a simple and powerful dependency manager that allows you to retrieve the same class as your Bloc or Controller with just 1 lines of code, no Provider context, no inheritedWidget:\n\n```dart\nController controller = Get.put(Controller()); \u002F\u002F Rather Controller controller = Controller();\n```\n\n- Note: If you are using Get's State Manager, pay more attention to the bindings API, which will make it easier to connect your view to your controller.\n\nInstead of instantiating your class within the class you are using, you are instantiating it within the Get instance, which will make it available throughout your App.\nSo you can use your controller (or class Bloc) normally\n\n**Tip:** Get dependency management is decoupled from other parts of the package, so if for example, your app is already using a state manager (any one, it doesn't matter), you don't need to rewrite it all, you can use this dependency injection with no problems at all\n\n```dart\ncontroller.fetchApi();\n```\n\nImagine that you have navigated through numerous routes, and you need data that was left behind in your controller, you would need a state manager combined with the Provider or Get_it, correct? Not with Get. You just need to ask Get to \"find\" for your controller, you don't need any additional dependencies:\n\n```dart\nController controller = Get.find();\n\u002F\u002FYes, it looks like Magic, Get will find your controller, and will deliver it to you. You can have 1 million controllers instantiated, Get will always give you the right controller.\n```\n\nAnd then you will be able to recover your controller data that was obtained back there:\n\n```dart\nText(controller.textFromApi);\n```\n\n### More details about dependency management\n\n**See a more in-depth explanation of dependency management [here](.\u002Fdocumentation\u002Fen_US\u002Fdependency_management.md)**\n\n# Utils\n\n## Internationalization\n\n### Translations\n\nTranslations are kept as a simple key-value dictionary map.\nTo add custom translations, create a class and extend `Translations`.\n\n```dart\nimport 'package:get\u002Fget.dart';\n\nclass Messages extends Translations {\n  @override\n  Map\u003CString, Map\u003CString, String>> get keys => {\n        'en_US': {\n          'hello': 'Hello World',\n        },\n        'de_DE': {\n          'hello': 'Hallo Welt',\n        }\n      };\n}\n```\n\n#### Using translations\n\nJust append `.tr` to the specified key and it will be translated, using the current value of `Get.locale` and `Get.fallbackLocale`.\n\n```dart\nText('title'.tr);\n```\n\n#### Using translation with singular and plural\n\n```dart\nvar products = [];\nText('singularKey'.trPlural('pluralKey', products.length, Args));\n```\n\n#### Using translation with parameters\n\n```dart\nimport 'package:get\u002Fget.dart';\n\n\nMap\u003CString, Map\u003CString, String>> get keys => {\n    'en_US': {\n        'logged_in': 'logged in as @name with email @email',\n    },\n    'es_ES': {\n       'logged_in': 'iniciado sesión como @name con e-mail @email',\n    }\n};\n\nText('logged_in'.trParams({\n  'name': 'Jhon',\n  'email': 'jhon@example.com'\n  }));\n```\n\n### Locales\n\nPass parameters to `GetMaterialApp` to define the locale and translations.\n\n```dart\nreturn GetMaterialApp(\n    translations: Messages(), \u002F\u002F your translations\n    locale: Locale('en', 'US'), \u002F\u002F translations will be displayed in that locale\n    fallbackLocale: Locale('en', 'UK'), \u002F\u002F specify the fallback locale in case an invalid locale is selected.\n);\n```\n\n#### Change locale\n\nCall `Get.updateLocale(locale)` to update the locale. Translations then automatically use the new locale.\n\n```dart\nvar locale = Locale('en', 'US');\nGet.updateLocale(locale);\n```\n\n#### System locale\n\nTo read the system locale, you could use `Get.deviceLocale`.\n\n```dart\nreturn GetMaterialApp(\n    locale: Get.deviceLocale,\n);\n```\n\n## Change Theme\n\nPlease do not use any higher level widget than `GetMaterialApp` in order to update it. This can trigger duplicate keys. A lot of people are used to the prehistoric approach of creating a \"ThemeProvider\" widget just to change the theme of your app, and this is definitely NOT necessary with **GetX™**.\n\nYou can create your custom theme and simply add it within `Get.changeTheme` without any boilerplate for that:\n\n```dart\nGet.changeTheme(ThemeData.light());\n```\n\nIf you want to create something like a button that changes the Theme in `onTap`, you can combine two **GetX™** APIs for that:\n\n- The api that checks if the dark `Theme` is being used.\n- And the `Theme` Change API, you can just put this within an `onPressed`:\n\n```dart\nGet.changeTheme(Get.isDarkMode? ThemeData.light(): ThemeData.dark());\n```\n\nWhen `.darkmode` is activated, it will switch to the _light theme_, and when the _light theme_ becomes active, it will change to _dark theme_.\n\n## GetConnect\n\nGetConnect is an easy way to communicate from your back to your front with http or websockets\n\n### Default configuration\n\nYou can simply extend GetConnect and use the GET\u002FPOST\u002FPUT\u002FDELETE\u002FSOCKET methods to communicate with your Rest API or websockets.\n\n```dart\nclass UserProvider extends GetConnect {\n  \u002F\u002F Get request\n  Future\u003CResponse> getUser(int id) => get('http:\u002F\u002Fyouapi\u002Fusers\u002F$id');\n  \u002F\u002F Post request\n  Future\u003CResponse> postUser(Map data) => post('http:\u002F\u002Fyouapi\u002Fusers', body: data);\n  \u002F\u002F Post request with File\n  Future\u003CResponse\u003CCasesModel>> postCases(List\u003Cint> image) {\n    final form = FormData({\n      'file': MultipartFile(image, filename: 'avatar.png'),\n      'otherFile': MultipartFile(image, filename: 'cover.png'),\n    });\n    return post('http:\u002F\u002Fyouapi\u002Fusers\u002Fupload', form);\n  }\n\n  GetSocket userMessages() {\n    return socket('https:\u002F\u002Fyourapi\u002Fusers\u002Fsocket');\n  }\n}\n```\n\n### Custom configuration\n\nGetConnect is highly customizable You can define base Url, as answer modifiers, as Requests modifiers, define an authenticator, and even the number of attempts in which it will try to authenticate itself, in addition to giving the possibility to define a standard decoder that will transform all your requests into your Models without any additional configuration.\n\n```dart\nclass HomeProvider extends GetConnect {\n  @override\n  void onInit() {\n    \u002F\u002F All request will pass to jsonEncode so CasesModel.fromJson()\n    httpClient.defaultDecoder = CasesModel.fromJson;\n    httpClient.baseUrl = 'https:\u002F\u002Fapi.covid19api.com';\n    \u002F\u002F baseUrl = 'https:\u002F\u002Fapi.covid19api.com'; \u002F\u002F It define baseUrl to\n    \u002F\u002F Http and websockets if used with no [httpClient] instance\n\n    \u002F\u002F It's will attach 'apikey' property on header from all requests\n    httpClient.addRequestModifier((request) {\n      request.headers['apikey'] = '12345678';\n      return request;\n    });\n\n    \u002F\u002F Even if the server sends data from the country \"Brazil\",\n    \u002F\u002F it will never be displayed to users, because you remove\n    \u002F\u002F that data from the response, even before the response is delivered\n    httpClient.addResponseModifier\u003CCasesModel>((request, response) {\n      CasesModel model = response.body;\n      if (model.countries.contains('Brazil')) {\n        model.countries.remove('Brazilll');\n      }\n    });\n\n    httpClient.addAuthenticator((request) async {\n      final response = await get(\"http:\u002F\u002Fyourapi\u002Ftoken\");\n      final token = response.body['token'];\n      \u002F\u002F Set the header\n      request.headers['Authorization'] = \"$token\";\n      return request;\n    });\n\n    \u002F\u002FAutenticator will be called 3 times if HttpStatus is\n    \u002F\u002FHttpStatus.unauthorized\n    httpClient.maxAuthRetries = 3;\n  }\n\n  @override\n  Future\u003CResponse\u003CCasesModel>> getCases(String path) => get(path);\n}\n```\n\n## GetPage Middleware\n\nThe GetPage has now new property that takes a list of GetMiddleWare and run them in the specific order.\n\n**Note**: When GetPage has a Middlewares, all the children of this page will have the same middlewares automatically.\n\n### Priority\n\nThe Order of the Middlewares to run can be set by the priority in the GetMiddleware.\n\n```dart\nfinal middlewares = [\n  GetMiddleware(priority: 2),\n  GetMiddleware(priority: 5),\n  GetMiddleware(priority: 4),\n  GetMiddleware(priority: -8),\n];\n```\n\nthose middlewares will be run in this order **-8 => 2 => 4 => 5**\n\n### Redirect\n\nThis function will be called when the page of the called route is being searched for. It takes RouteSettings as a result to redirect to. Or give it null and there will be no redirecting.\n\n```dart\nRouteSettings redirect(String route) {\n  final authService = Get.find\u003CAuthService>();\n  return authService.authed.value ? null : RouteSettings(name: '\u002Flogin')\n}\n```\n\n### onPageCalled\n\nThis function will be called when this Page is called before anything created\nyou can use it to change something about the page or give it new page\n\n```dart\nGetPage onPageCalled(GetPage page) {\n  final authService = Get.find\u003CAuthService>();\n  return page.copyWith(title: 'Welcome ${authService.UserName}');\n}\n```\n\n### OnBindingsStart\n\nThis function will be called right before the Bindings are initialize.\nHere you can change Bindings for this page.\n\n```dart\nList\u003CBindings> onBindingsStart(List\u003CBindings> bindings) {\n  final authService = Get.find\u003CAuthService>();\n  if (authService.isAdmin) {\n    bindings.add(AdminBinding());\n  }\n  return bindings;\n}\n```\n\n### OnPageBuildStart\n\nThis function will be called right after the Bindings are initialize.\nHere you can do something after that you created the bindings and before creating the page widget.\n\n```dart\nGetPageBuilder onPageBuildStart(GetPageBuilder page) {\n  print('bindings are ready');\n  return page;\n}\n```\n\n### OnPageBuilt\n\nThis function will be called right after the GetPage.page function is called and will give you the result of the function. and take the widget that will be showed.\n\n### OnPageDispose\n\nThis function will be called right after disposing all the related objects (Controllers, views, ...) of the page.\n\n## Other Advanced APIs\n\n```dart\n\u002F\u002F give the current args from currentScreen\nGet.arguments\n\n\u002F\u002F give name of previous route\nGet.previousRoute\n\n\u002F\u002F give the raw route to access for example, rawRoute.isFirst()\nGet.rawRoute\n\n\u002F\u002F give access to Routing API from GetObserver\nGet.routing\n\n\u002F\u002F check if snackbar is open\nGet.isSnackbarOpen\n\n\u002F\u002F check if dialog is open\nGet.isDialogOpen\n\n\u002F\u002F check if bottomsheet is open\nGet.isBottomSheetOpen\n\n\u002F\u002F remove one route.\nGet.removeRoute()\n\n\u002F\u002F back repeatedly until the predicate returns true.\nGet.until()\n\n\u002F\u002F go to next route and remove all the previous routes until the predicate returns true.\nGet.offUntil()\n\n\u002F\u002F go to next named route and remove all the previous routes until the predicate returns true.\nGet.offNamedUntil()\n\n\u002F\u002FCheck in what platform the app is running\nGetPlatform.isAndroid\nGetPlatform.isIOS\nGetPlatform.isMacOS\nGetPlatform.isWindows\nGetPlatform.isLinux\nGetPlatform.isFuchsia\n\n\u002F\u002FCheck the device type\nGetPlatform.isMobile\nGetPlatform.isDesktop\n\u002F\u002FAll platforms are supported independently in web!\n\u002F\u002FYou can tell if you are running inside a browser\n\u002F\u002Fon Windows, iOS, OSX, Android, etc.\nGetPlatform.isWeb\n\n\n\u002F\u002F Equivalent to : MediaQuery.of(context).size.height,\n\u002F\u002F but immutable.\nGet.height\nGet.width\n\n\u002F\u002F Gives the current context of the Navigator.\nGet.context\n\n\u002F\u002F Gives the context of the snackbar\u002Fdialog\u002Fbottomsheet in the foreground, anywhere in your code.\nGet.contextOverlay\n\n\u002F\u002F Note: the following methods are extensions on context. Since you\n\u002F\u002F have access to context in any place of your UI, you can use it anywhere in the UI code\n\n\u002F\u002F If you need a changeable height\u002Fwidth (like Desktop or browser windows that can be scaled) you will need to use context.\ncontext.width\ncontext.height\n\n\u002F\u002F Gives you the power to define half the screen, a third of it and so on.\n\u002F\u002F Useful for responsive applications.\n\u002F\u002F param dividedBy (double) optional - default: 1\n\u002F\u002F param reducedBy (double) optional - default: 0\ncontext.heightTransformer()\ncontext.widthTransformer()\n\n\u002F\u002F\u002F Similar to MediaQuery.sizeOf(context);\ncontext.mediaQuerySize()\n\n\u002F\u002F\u002F Similar to MediaQuery.paddingOf(context);\ncontext.mediaQueryPadding()\n\n\u002F\u002F\u002F Similar to MediaQuery.viewPaddingOf(context);\ncontext.mediaQueryViewPadding()\n\n\u002F\u002F\u002F Similar to MediaQuery.viewInsetsOf(context);\ncontext.mediaQueryViewInsets()\n\n\u002F\u002F\u002F Similar to MediaQuery.orientationOf(context);\ncontext.orientation()\n\n\u002F\u002F\u002F Check if device is on landscape mode\ncontext.isLandscape()\n\n\u002F\u002F\u002F Check if device is on portrait mode\ncontext.isPortrait()\n\n\u002F\u002F\u002F Similar to MediaQuery.devicePixelRatioOf(context);\ncontext.devicePixelRatio()\n\n\u002F\u002F\u002F Similar to MediaQuery.textScaleFactorOf(context);\ncontext.textScaleFactor()\n\n\u002F\u002F\u002F Get the shortestSide from screen\ncontext.mediaQueryShortestSide()\n\n\u002F\u002F\u002F True if width be larger than 800\ncontext.showNavbar()\n\n\u002F\u002F\u002F True if the shortestSide is smaller than 600p\ncontext.isPhone()\n\n\u002F\u002F\u002F True if the shortestSide is largest than 600p\ncontext.isSmallTablet()\n\n\u002F\u002F\u002F True if the shortestSide is largest than 720p\ncontext.isLargeTablet()\n\n\u002F\u002F\u002F True if the current device is Tablet\ncontext.isTablet()\n\n\u002F\u002F\u002F Returns a value\u003CT> according to the screen size\n\u002F\u002F\u002F can give value for:\n\u002F\u002F\u002F watch: if the shortestSide is smaller than 300\n\u002F\u002F\u002F mobile: if the shortestSide is smaller than 600\n\u002F\u002F\u002F tablet: if the shortestSide is smaller than 1200\n\u002F\u002F\u002F desktop: if width is largest than 1200\ncontext.responsiveValue\u003CT>()\n```\n\n### Optional Global Settings and Manual configurations\n\nGetMaterialApp configures everything for you, but if you want to configure Get manually.\n\n```dart\nMaterialApp(\n  navigatorKey: Get.key,\n  navigatorObservers: [GetObserver()],\n);\n```\n\nYou will also be able to use your own Middleware within `GetObserver`, this will not influence anything.\n\n```dart\nMaterialApp(\n  navigatorKey: Get.key,\n  navigatorObservers: [\n    GetObserver(MiddleWare.observer) \u002F\u002F Here\n  ],\n);\n```\n\nYou can create _Global Settings_ for `Get`. Just add `Get.config` to your code before pushing any route.\nOr do it directly in your `GetMaterialApp`\n\n```dart\nGetMaterialApp(\n  enableLog: true,\n  defaultTransition: Transition.fade,\n  opaqueRoute: Get.isOpaqueRouteDefault,\n  popGesture: Get.isPopGestureEnable,\n  transitionDuration: Get.defaultDurationTransition,\n  defaultGlobalState: Get.defaultGlobalState,\n);\n\nGet.config(\n  enableLog = true,\n  defaultPopGesture = true,\n  defaultTransition = Transitions.cupertino\n)\n```\n\nYou can optionally redirect all the logging messages from `Get`.\nIf you want to use your own, favourite logging package,\nand want to capture the logs there:\n\n```dart\nGetMaterialApp(\n  enableLog: true,\n  logWriterCallback: localLogWriter,\n);\n\nvoid localLogWriter(String text, {bool isError = false}) {\n  \u002F\u002F pass the message to your favourite logging package here\n  \u002F\u002F please note that even if enableLog: false log messages will be pushed in this callback\n  \u002F\u002F you get check the flag if you want through GetConfig.isLogEnable\n}\n\n```\n\n### Local State Widgets\n\nThese Widgets allows you to manage a single value, and keep the state ephemeral and locally.\nWe have flavours for Reactive and Simple.\nFor instance, you might use them to toggle obscureText in a `TextField`, maybe create a custom\nExpandable Panel, or maybe modify the current index in `BottomNavigationBar` while changing the content\nof the body in a `Scaffold`.\n\n#### ValueBuilder\n\nA simplification of `StatefulWidget` that works with a `.setState` callback that takes the updated value.\n\n```dart\nValueBuilder\u003Cbool>(\n  initialValue: false,\n  builder: (value, updateFn) => Switch(\n    value: value,\n    onChanged: updateFn, \u002F\u002F same signature! you could use ( newValue ) => updateFn( newValue )\n  ),\n  \u002F\u002F if you need to call something outside the builder method.\n  onUpdate: (value) => print(\"Value updated: $value\"),\n  onDispose: () => print(\"Widget unmounted\"),\n),\n```\n\n#### ObxValue\n\nSimilar to [`ValueBuilder`](#valuebuilder), but this is the Reactive version, you pass a Rx instance (remember the magical .obs?) and\nupdates automatically... isn't it awesome?\n\n```dart\nObxValue((data) => Switch(\n        value: data.value,\n        onChanged: data, \u002F\u002F Rx has a _callable_ function! You could use (flag) => data.value = flag,\n    ),\n    false.obs,\n),\n```\n\n## Useful tips\n\n`.obs`ervables (also known as _Rx_ Types) have a wide variety of internal methods and operators.\n\n> Is very common to _believe_ that a property with `.obs` **IS** the actual value... but make no mistake!\n> We avoid the Type declaration of the variable, because Dart's compiler is smart enough, and the code\n> looks cleaner, but:\n\n```dart\nvar message = 'Hello world'.obs;\nprint( 'Message \"$message\" has Type ${message.runtimeType}');\n```\n\nEven if `message` _prints_ the actual String value, the Type is **RxString**!\n\nSo, you can't do `message.substring( 0, 4 )`.\nYou have to access the real `value` inside the _observable_:\nThe most \"used way\" is `.value`, but, did you know that you can also use...\n\n```dart\nfinal name = 'GetX'.obs;\n\u002F\u002F only \"updates\" the stream, if the value is different from the current one.\nname.value = 'Hey';\n\n\u002F\u002F All Rx properties are \"callable\" and returns the new value.\n\u002F\u002F but this approach does not accepts `null`, the UI will not rebuild.\nname('Hello');\n\n\u002F\u002F is like a getter, prints 'Hello'.\nname() ;\n\n\u002F\u002F\u002F numbers:\n\nfinal count = 0.obs;\n\n\u002F\u002F You can use all non mutable operations from num primitives!\ncount + 1;\n\n\u002F\u002F Watch out! this is only valid if `count` is not final, but var\ncount += 1;\n\n\u002F\u002F You can also compare against values:\ncount > 2;\n\n\u002F\u002F\u002F booleans:\n\nfinal flag = false.obs;\n\n\u002F\u002F switches the value between true\u002Ffalse\nflag.toggle();\n\n\n\u002F\u002F\u002F all types:\n\n\u002F\u002F Sets the `value` to null.\nflag.nil();\n\n\u002F\u002F All toString(), toJson() operations are passed down to the `value`\nprint( count ); \u002F\u002F calls `toString()` inside  for RxInt\n\nfinal abc = [0,1,2].obs;\n\u002F\u002F Converts the value to a json Array, prints RxList\n\u002F\u002F Json is supported by all Rx types!\nprint('json: ${jsonEncode(abc)}, type: ${abc.runtimeType}');\n\n\u002F\u002F RxMap, RxList and RxSet are special Rx types, that extends their native types.\n\u002F\u002F but you can work with a List as a regular list, although is reactive!\nabc.add(12); \u002F\u002F pushes 12 to the list, and UPDATES the stream.\nabc[3]; \u002F\u002F like Lists, reads the index 3.\n\n\n\u002F\u002F equality works with the Rx and the value, but hashCode is always taken from the value\nfinal number = 12.obs;\nprint( number == 12 ); \u002F\u002F prints > true\n\n\u002F\u002F\u002F Custom Rx Models:\n\n\u002F\u002F toJson(), toString() are deferred to the child, so you can implement override on them, and print() the observable directly.\n\nclass User {\n    String name, last;\n    int age;\n    User({this.name, this.last, this.age});\n\n    @override\n    String toString() => '$name $last, $age years old';\n}\n\nfinal user = User(name: 'John', last: 'Doe', age: 33).obs;\n\n\u002F\u002F `user` is \"reactive\", but the properties inside ARE NOT!\n\u002F\u002F So, if we change some variable inside of it...\nuser.value.name = 'Roi';\n\u002F\u002F The widget will not rebuild!,\n\u002F\u002F `Rx` don't have any clue when you change something inside user.\n\u002F\u002F So, for custom classes, we need to manually \"notify\" the change.\nuser.refresh();\n\n\u002F\u002F or we can use the `update()` method!\nuser.update((value){\n  value.name='Roi';\n});\n\nprint( user );\n```\n\n## StateMixin\n\nAnother way to handle your `UI` state is use the `StateMixin\u003CT>` .\nTo implement it, use the `with` to add the `StateMixin\u003CT>`\nto your controller which allows a T model.\n\n```dart\nclass Controller extends GetController with StateMixin\u003CUser>{}\n```\n\nThe `change()` method change the State whenever we want.\nJust pass the data and the status in this way:\n\n```dart\nchange(data, status: RxStatus.success());\n```\n\nRxStatus allow these status:\n\n```dart\nRxStatus.loading();\nRxStatus.success();\nRxStatus.empty();\nRxStatus.error('message');\n```\n\nTo represent it in the UI, use:\n\n```dart\nclass OtherClass extends GetView\u003CController> {\n  @override\n  Widget build(BuildContext context) {\n    return Scaffold(\n\n      body: controller.obx(\n        (state)=>Text(state.name),\n\n        \u002F\u002F here you can put your custom loading indicator, but\n        \u002F\u002F by default would be Center(child:CircularProgressIndicator())\n        onLoading: CustomLoadingIndicator(),\n        onEmpty: Text('No data found'),\n\n        \u002F\u002F here also you can set your own error widget, but by\n        \u002F\u002F default will be an Center(child:Text(error))\n        onError: (error)=>Text(error),\n      ),\n    );\n}\n```\n\n#### GetView\n\nI love this Widget, is so simple, yet, so useful!\n\nIs a `const Stateless` Widget that has a getter `controller` for a registered `Controller`, that's all.\n\n```dart\n class AwesomeController extends GetController {\n   final String title = 'My Awesome View';\n }\n\n  \u002F\u002F ALWAYS remember to pass the `Type` you used to register your controller!\n class AwesomeView extends GetView\u003CAwesomeController> {\n   @override\n   Widget build(BuildContext context) {\n     return Container(\n       padding: EdgeInsets.all(20),\n       child: Text(controller.title), \u002F\u002F just call `controller.something`\n     );\n   }\n }\n```\n\n#### GetResponsiveView\n\nExtend this widget to build responsive view.\nthis widget contains the `screen` property that have all\ninformation about the screen size and type.\n\n##### How to use it\n\nYou have two options to build it.\n\n- with `builder` method you return the widget to build.\n- with methods `desktop`, `tablet`,`phone`, `watch`. the specific\n  method will be built when the screen type matches the method\n  when the screen is [ScreenType.Tablet] the `tablet` method\n  will be exuded and so on.\n  **Note:** If you use this method please set the property `alwaysUseBuilder` to `false`\n\nWith `settings` property you can set the width limit for the screen types.\n\n![example](https:\u002F\u002Fgithub.com\u002FSchabanBo\u002Fget_page_example\u002Fblob\u002Fmaster\u002Fdocs\u002FExample.gif?raw=true)\nCode to this screen\n[code](https:\u002F\u002Fgithub.com\u002FSchabanBo\u002Fget_page_example\u002Fblob\u002Fmaster\u002Flib\u002Fpages\u002Fresponsive_example\u002Fresponsive_view.dart)\n\n#### GetWidget\n\nMost people have no idea about this Widget, or totally confuse the usage of it.\nThe use case is very rare, but very specific: It `caches` a Controller.\nBecause of the _cache_, can't be a `const Stateless`.\n\n> So, when do you need to \"cache\" a Controller?\n\nIf you use, another \"not so common\" feature of **GetX**: `Get.create()`.\n\n`Get.create(()=>Controller())` will generate a new `Controller` each time you call\n`Get.find\u003CController>()`,\n\nThat's where `GetWidget` shines... as you can use it, for example,\nto keep a list of Todo items. So, if the widget gets \"rebuilt\", it will keep the same controller instance.\n\n#### GetxService\n\nThis class is like a `GetxController`, it shares the same lifecycle ( `onInit()`, `onReady()`, `onClose()`).\nBut has no \"logic\" inside of it. It just notifies **GetX** Dependency Injection system, that this subclass\n**can not** be removed from memory.\n\nSo is super useful to keep your \"Services\" always reachable and active with `Get.find()`. Like:\n`ApiService`, `StorageService`, `CacheService`.\n\n```dart\nFuture\u003Cvoid> main() async {\n  await initServices(); \u002F\u002F\u002F AWAIT SERVICES INITIALIZATION.\n  runApp(SomeApp());\n}\n\n\u002F\u002F\u002F Is a smart move to make your Services intiialize before you run the Flutter app.\n\u002F\u002F\u002F as you can control the execution flow (maybe you need to load some Theme configuration,\n\u002F\u002F\u002F apiKey, language defined by the User... so load SettingService before running ApiService.\n\u002F\u002F\u002F so GetMaterialApp() doesnt have to rebuild, and takes the values directly.\nvoid initServices() async {\n  print('starting services ...');\n  \u002F\u002F\u002F Here is where you put get_storage, hive, shared_pref initialization.\n  \u002F\u002F\u002F or moor connection, or whatever that's async.\n  await Get.putAsync(() => DbService().init());\n  await Get.putAsync(SettingsService()).init();\n  print('All services started...');\n}\n\nclass DbService extends GetxService {\n  Future\u003CDbService> init() async {\n    print('$runtimeType delays 2 sec');\n    await 2.delay();\n    print('$runtimeType ready!');\n    return this;\n  }\n}\n\nclass SettingsService extends GetxService {\n  void init() async {\n    print('$runtimeType delays 1 sec');\n    await 1.delay();\n    print('$runtimeType ready!');\n  }\n}\n\n```\n\nThe only way to actually delete a `GetxService`, is with `Get.reset()` which is like a\n\"Hot Reboot\" of your app. So remember, if you need absolute persistence of a class instance during the\nlifetime of your app, use `GetxService`.\n\n### Tests\n\nYou can test your controllers like any other class, including their lifecycles:\n\n```dart\nclass Controller extends GetxController {\n  @override\n  void onInit() {\n    super.onInit();\n    \u002F\u002FChange value to name2\n    name.value = 'name2';\n  }\n\n  @override\n  void onClose() {\n    name.value = '';\n    super.onClose();\n  }\n\n  final name = 'name1'.obs;\n\n  void changeName() => name.value = 'name3';\n}\n\nvoid main() {\n  test('''\nTest the state of the reactive variable \"name\" across all of its lifecycles''',\n      () {\n    \u002F\u002F\u002F You can test the controller without the lifecycle,\n    \u002F\u002F\u002F but it's not recommended unless you're not using\n    \u002F\u002F\u002F  GetX dependency injection\n    final controller = Controller();\n    expect(controller.name.value, 'name1');\n\n    \u002F\u002F\u002F If you are using it, you can test everything,\n    \u002F\u002F\u002F including the state of the application after each lifecycle.\n    Get.put(controller); \u002F\u002F onInit was called\n    expect(controller.name.value, 'name2');\n\n    \u002F\u002F\u002F Test your functions\n    controller.changeName();\n    expect(controller.name.value, 'name3');\n\n    \u002F\u002F\u002F onClose was called\n    Get.delete\u003CController>();\n\n    expect(controller.name.value, '');\n  });\n}\n```\n\n#### Tips\n\n##### Mockito or mocktail\n\nIf you need to mock your GetxController\u002FGetxService, you should extend GetxController, and mixin it with Mock, that way\n\n```dart\nclass NotificationServiceMock extends GetxService with Mock implements NotificationService {}\n```\n\n##### Using Get.reset()\n\nIf you are testing widgets, or test groups, use Get.reset at the end of your test or in tearDown to reset all settings from your previous test.\n\n##### Get.testMode\n\nif you are using your navigation in your controllers, use `Get.testMode = true` at the beginning of your main.\n\n# Breaking changes from 2.0\n\n1- Rx types:\n\n| Before  | After      |\n| ------- | ---------- |\n| StringX | `RxString` |\n| IntX    | `RxInt`    |\n| MapX    | `RxMap`    |\n| ListX   | `RxList`   |\n| NumX    | `RxNum`    |\n| DoubleX | `RxDouble` |\n\nRxController and GetBuilder now have merged, you no longer need to memorize which controller you want to use, just use GetxController, it will work for simple state management and for reactive as well.\n\n2- NamedRoutes\nBefore:\n\n```dart\nGetMaterialApp(\n  namedRoutes: {\n    '\u002F': GetRoute(page: Home()),\n  }\n)\n```\n\nNow:\n\n```dart\nGetMaterialApp(\n  getPages: [\n    GetPage(name: '\u002F', page: () => Home()),\n  ]\n)\n```\n\nWhy this change?\nOften, it may be necessary to decide which page will be displayed from a parameter, or a login token, the previous approach was inflexible, as it did not allow this.\nInserting the page into a function has significantly reduced the RAM consumption, since the routes will not be allocated in memory since the app was started, and it also allowed to do this type of approach:\n\n```dart\n\nGetStorage box = GetStorage();\n\nGetMaterialApp(\n  getPages: [\n    GetPage(name: '\u002F', page:(){\n      return box.hasData('token') ? Home() : Login();\n    })\n  ]\n)\n```\n\n# Why Getx?\n\n1- Many times after a Flutter update, many of your packages will break. Sometimes compilation errors happen, errors often appear that there are still no answers about, and the developer needs to know where the error came from, track the error, only then try to open an issue in the corresponding repository, and see its problem solved. Get centralizes the main resources for development (State, dependency and route management), allowing you to add a single package to your pubspec, and start working. After a Flutter update, the only thing you need to do is update the Get dependency, and get to work. Get also resolves compatibility issues. How many times a version of a package is not compatible with the version of another, because one uses a dependency in one version, and the other in another version? This is also not a concern using Get, as everything is in the same package and is fully compatible.\n\n2- Flutter is easy, Flutter is incredible, but Flutter still has some boilerplate that may be unwanted for most developers, such as `Navigator.of(context).push (context, builder [...]`. Get simplifies development. Instead of writing 8 lines of code to just call a route, you can just do it: `Get.to(Home())` and you're done, you'll go to the next page. Dynamic web urls are a really painful thing to do with Flutter currently, and that with GetX is stupidly simple. Managing states in Flutter, and managing dependencies is also something that generates a lot of discussion, as there are hundreds of patterns in the pub. But there is nothing as easy as adding a \".obs\" at the end of your variable, and place your widget inside an Obx, and that's it, all updates to that variable will be automatically updated on the screen.\n\n3- Ease without worrying about performance. Flutter's performance is already amazing, but imagine that you use a state manager, and a locator to distribute your blocs\u002Fstores\u002Fcontrollers\u002F etc. classes. You will have to manually call the exclusion of that dependency when you don't need it. But have you ever thought of simply using your controller, and when it was no longer being used by anyone, it would simply be deleted from memory? That's what GetX does. With SmartManagement, everything that is not being used is deleted from memory, and you shouldn't have to worry about anything but programming. You will be assured that you are consuming the minimum necessary resources, without even having created a logic for this.\n\n4- Actual decoupling. You may have heard the concept \"separate the view from the business logic\". This is not a peculiarity of BLoC, MVC, MVVM, and any other standard on the market has this concept. However, this concept can often be mitigated in Flutter due to the use of context.\nIf you need context to find an InheritedWidget, you need it in the view, or pass the context by parameter. I particularly find this solution very ugly, and to work in teams we will always have a dependence on View's business logic. Getx is unorthodox with the standard approach, and while it does not completely ban the use of StatefulWidgets, InitState, etc., it always has a similar approach that can be cleaner. Controllers have life cycles, and when you need to make an APIREST request for example, you don't depend on anything in the view. You can use onInit to initiate the http call, and when the data arrives, the variables will be populated. As GetX is fully reactive (really, and works under streams), once the items are filled, all widgets that use that variable will be automatically updated in the view. This allows people with UI expertise to work only with widgets, and not have to send anything to business logic other than user events (like clicking a button), while people working with business logic will be free to create and test the business logic separately.\n\nThis library will always be updated and implementing new features. Feel free to offer PRs and contribute to them.\n\n# Community\n\n## Community channels\n\nGetX has a highly active and helpful community. If you have questions, or would like any assistance regarding the use of this framework, please join our community channels, your question will be answered more quickly, and it will be the most suitable place. This repository is exclusive for opening issues, and requesting resources, but feel free to be part of GetX Community.\n\n| **Slack**                                                                                                                   | **Discord**                                                                                                                 | **Telegram**                                                                                                          |\n| :-------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------- |\n| [![Get on Slack](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fslack-join-orange.svg)](https:\u002F\u002Fcommunityinviter.com\u002Fapps\u002Fgetxworkspace\u002Fgetx) | [![Discord Shield](https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F722900883784073290.svg?logo=discord)](https:\u002F\u002Fdiscord.com\u002Finvite\u002F9Hpt99N) | [![Telegram](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fchat-on%20Telegram-blue.svg)](https:\u002F\u002Ft.me\u002Fjoinchat\u002FPhdbJRmsZNpAqSLJL6bH7g) |\n\n## How to contribute\n\n_Want to contribute to the project? We will be proud to highlight you as one of our collaborators. Here are some points where you can contribute and make Get (and Flutter) even better._\n\n- Helping to translate the readme into other languages.\n- Adding documentation to the readme (a lot of Get's functions haven't been documented yet).\n- Write articles or make videos teaching how to use Get (they will be inserted in the Readme and in the future in our Wiki).\n- Offering PRs for code\u002Ftests.\n- Including new functions.\n\nAny contribution is welcome!\n\n## Articles and videos\n\n- [Flutter Getx EcoSystem package for arabic people](https:\u002F\u002Fwww.youtube.com\u002Fplaylist?list=PLV1fXIAyjeuZ6M8m56zajMUwu4uE3-SL0) - Tutorial by [Pesa Coder](https:\u002F\u002Fgithub.com\u002FUsamaElgendy).\n- [Dynamic Themes in 3 lines using GetX™](https:\u002F\u002Fmedium.com\u002Fswlh\u002Fflutter-dynamic-themes-in-3-lines-c3b375f292e3) - Tutorial by [Rod Brown](https:\u002F\u002Fgithub.com\u002FRodBr).\n- [Complete GetX™ Navigation](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=RaqPIoJSTtI) - Route management video by Amateur Coder.\n- [Complete GetX State Management](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=CNpXbeI_slw) - State management video by Amateur Coder.\n- [GetX™ Other Features](https:\u002F\u002Fyoutu.be\u002FttQtlX_Q0eU) - Utils, storage, bindings and other features video by Amateur Coder.\n- [Firestore User with GetX | Todo App](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=BiV0DcXgk58) - Video by Amateur Coder.\n- [Firebase Auth with GetX | Todo App](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=-H-T_BSgfOE) - Video by Amateur Coder.\n- [The Flutter GetX™ Ecosystem ~ State Management](https:\u002F\u002Fmedium.com\u002Fflutter-community\u002Fthe-flutter-getx-ecosystem-state-management-881c7235511d) - State management by [Aachman Garg](https:\u002F\u002Fgithub.com\u002Fimaachman).\n- [The Flutter GetX™ Ecosystem ~ Dependency Injection](https:\u002F\u002Fmedium.com\u002Fflutter-community\u002Fthe-flutter-getx-ecosystem-dependency-injection-8e763d0ec6b9) - Dependency Injection by [Aachman Garg](https:\u002F\u002Fgithub.com\u002Fimaachman).\n- [GetX, the all-in-one Flutter package](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=IYQgtu9TM74) - A brief tutorial covering State Management and Navigation by Thad Carnevalli.\n- [Build a To-do List App from scratch using Flutter and GetX](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=EcnqFasHf18) - UI + State Management + Storage video by Thad Carnevalli.\n- [GetX Flutter Firebase Auth Example](https:\u002F\u002Fmedium.com\u002F@jeffmcmorris\u002Fgetx-flutter-firebase-auth-example-b383c1dd1de2) - Article by Jeff McMorris.\n- [Flutter State Management with GetX – Complete App](https:\u002F\u002Fwww.appwithflutter.com\u002Fflutter-state-management-with-getx\u002F) - by App With Flutter.\n- [Flutter Routing with Animation using Get Package](https:\u002F\u002Fwww.appwithflutter.com\u002Fflutter-routing-using-get-package\u002F) - by App With Flutter.\n- [A minimal example on dartpad](https:\u002F\u002Fdartpad.dev\u002F2b3d0d6f9d4e312c5fdbefc414c1727e?) - by [Roi Peker](https:\u002F\u002Fgithub.com\u002Froipeker)\n- [GetConnect: The best way to perform API operations in Flutter with Get.](https:\u002F\u002Fabsyz.com\u002Fgetconnect-the-best-way-to-perform-api-operations-in-flutter-with-getx\u002F) - by [MD Sarfaraj](https:\u002F\u002Fgithub.com\u002Fsocialmad)\n- [How To Create an App with GetX Architect in Flutter with Get CLI](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=7mb4qBA7kTk&t=1380s) - by [MD Sarfaraj](https:\u002F\u002Fgithub.com\u002Fsocialmad)\n","Getx 是一个用于 Flutter 应用开发的轻量级框架，它支持无上下文地打开屏幕、弹出框、对话框和底部工作表，并简化了状态管理和依赖注入。其核心功能包括路由管理、HTTP 请求处理、国际化支持以及简洁的状态管理模式。Getx 通过提供一系列高效且易于使用的工具来加速应用开发流程，特别适合需要快速构建跨平台移动或 Web 应用的场景。此外，该库遵循 MIT 许可证开源，拥有活跃的社区支持与丰富的文档资源。",2,"2026-06-11 03:21:11","top_language"]