Skip to content
pubscout

flutter_control

4.2.1+1, released 7 months ago by basecontrol.dev

A comprehensive framework for state management, dependency injection, routing, and localization.

WASM-ready
$ flutter pub add flutter_control
Source repository

What it does

Flutter Control is a modular framework that streamlines app architecture by combining state management, a built-in service locator, navigation, reactive observables, and localization support.

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

Use it when

  • You want an all-in-one framework for state management, DI, and routing without wiring multiple small packages.
  • You prefer modular architecture with independent modules and service locators.
  • You need reactive state bindings combined with custom lifecycle-aware widgets and hooks.

Skip it when

  • You prefer single-purpose libraries and want to choose your own state management or routing solution.
  • You want to avoid heavy framework lock-in.
  • You rely heavily on compile-time code generation for navigation or state models.

Strengths

  • Comprehensive ecosystem covering state, DI, navigation, and localization in one package.
  • Built-in Service Locator with Factory and Singleton patterns.
  • Reactive observables like ActionControl and FieldControl integrated with UI builders.
  • Context extensions and hooks for lazy initialization and clean lifecycle management.

Weaknesses

  • High level of framework lock-in due to its monolithic approach.
  • Extensive learning curve to understand all custom architectural concepts and base classes.

Setup

Kind
Flutter widgets
Effort
Low
Code generation
No
Direct dependencies
2

Initialize the core framework in main.dart using Control.initControl and wrap your app with ControlRoot.

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Control.initControl(
    entries: {
      MyService: MyService(),
    },
  );
  runApp(MyApp());
}

Alternatives

Packages that do the same job and could replace flutter_control.

  • go_router

    If you need a standard, declarative routing package maintained directly by the Flutter team instead of a framework-specific navigation system.

  • auto_route

    If you prefer code-generation-based type-safe routing and deep linking.