jonataslaw/getx

Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 5th, 2026
Created on November 14th, 2019
Open Issues & Pull Requests: 1,177 (+0)
GitHub issues: Enabled
Number of forks: 1,850
Total Stargazers: 11,198 (+0)
Total Subscribers: 127 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

GetX is a state management and dependency injection framework for Flutter that eliminates the need to pass context through widget trees.

GetX solves the problem of boilerplate-heavy state management and navigation in Flutter applications. It provides a reactive state management system where widgets automatically rebuild when observed state changes, without requiring explicit listener setup. The framework handles navigation by allowing developers to open screens, snackbars, dialogs, and bottom sheets through simple method calls rather than building widget trees. Dependency injection is built in, letting developers register and retrieve services globally without manual wiring. The approach centers on reducing ceremony: instead of wrapping widgets in providers or passing context down multiple levels, developers use Get's static methods to manage state, navigate, and access dependencies from anywhere in the application.

Developers should choose GetX if they want to minimize boilerplate in Flutter projects and prefer a more direct, imperative approach to navigation and state management. It suits applications of any size where reducing context passing and simplifying service access are priorities. The framework is particularly valuable for teams that want dependency injection and state management unified in a single solution rather than combining multiple packages. GetX also includes built-in support for internationalization and HTTP client functionality, reducing the need for additional dependencies.

The project maintains active development with regular updates addressing bug fixes and feature requests. The codebase shows consistent refinement of core functionality based on user feedback. Documentation is actively maintained to reflect current API usage patterns. The project demonstrates responsiveness to community issues and maintains backward compatibility while evolving the framework's capabilities.