Skip to content
pubscout

getxify

5.2.0, released 7 days ago by an unverified publisher

A toolkit for reactive state management, dependency injection, and routing without code generation.

WASM-readyUses material_ui
$ flutter pub add getxify
Source repository

What it does

Provides tools for managing app state using reactive observables (.obs) and Obx widgets, handling dependency injection lifecycle, and managing contextless or named navigation.

AI-written summary of version 5.1.2, based on the package's README and metadata. Report an inaccuracy

Use it when

  • You want lightweight reactive state management without boilerplate or code generation
  • You prefer contextless navigation and named route management
  • You are migrating from legacy GetX to a modernized Dart 3 compatible framework

Skip it when

  • Your team prefers strict unidirectional data flow architectures like BLoC or Redux
  • You want a modular ecosystem where routing and state management are decoupled

Strengths

  • Zero-boilerplate syntax with .obs and Obx widgets
  • Built-in lifecycle-aware dependency injection
  • Supports both contextless and nested route management with deep linking

Weaknesses

  • Global state access patterns can lead to tightly coupled code if misused
  • Relies heavily on global singletons for dependency injection

Setup

Kind
Flutter widgets
Effort
Low
Code generation
No
Direct dependencies
3

Not documented

void main() => runApp(GetMaterialApp(home: Home()));

class CounterController extends GetxController {
  var count = 0.obs;
  void increment() => count++;
}

class Home extends StatelessWidget {
  final c = Get.put(CounterController());

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Obx(() => Text('Clicks: ${c.count}'))),
      floatingActionButton: FloatingActionButton(
        onPressed: c.increment,
        child: const Icon(Icons.add),
      ),
    );
  }
}

Alternatives

Packages that do the same job and could replace getxify.

  • go_router

    If you prefer official, declarative routing rather than GetXify's imperative navigation.

Works with

Packages commonly used together with getxify: ones it builds on, ones built on it, and its own family.