air_framework 1.0.3
air_framework: ^1.0.3 copied to clipboard
A modular, reactive, and scalable framework for Flutter. Build industrial-grade apps with a decoupled architecture.
Air Framework π #
A modular, reactive, and scalable framework for Flutter. Build industrial-grade apps with a decoupled architecture inspired by enterprise app concepts.
Why Air Framework?
As apps grow, they become harder to maintain. Air Framework solves this by enforcing strict module boundaries, unidirectional data flow, and explicit dependencies. It's not just a state management library; it's a complete architecture for teams building large-scale Flutter applications.
β¨ Features #
| Feature | Description |
|---|---|
| π§© Modular Architecture | Self-contained, independent modules with clear boundaries |
| π Adapters | Headless service integrations (HTTP, analytics, error tracking) |
| β‘ Reactive State | Built-in state management using Air State controller with typed flows |
| π Dependency Injection | Type-safe DI with scoped services and lifecycle management |
| π Security | Permission system, secure logging, and audit trails |
| π£οΈ Routing | Integrated routing with go_router support |
| π οΈ DevTools | Built-in debugging panels for state, modules, adapters, and performance |
| π§ͺ Testing Utilities | Mock controllers and test helpers included |
ποΈ Architecture #
Every feature is a Module. Modules declare their dependencies explicitly and communicate via a typed Event Bus.
App Shell
βββ Notes Module
βββ Weather Module
βββ Dashboard Module
βββ depends on β Notes
βββ depends on β Weather
Core Framework
βββ AirDI (Dependency Injection)
βββ AirRouter (Routing)
βββ EventBus (Cross-module communication)
βββ AirState (Reactive state management)
βββ AdapterManager (Infrastructure services)
βββ DevTools (Debugging inspector)
π¦ Installation #
Add air_framework to your pubspec.yaml:
dependencies:
air_framework: # latest version from pub.dev
For the complete development experience, also install the CLI:
dart pub global activate air_cli
π Quick Start #
1. Create a Module #
Define a module by extending AppModule. This encapsulates your routes, bindings, and initialization logic.
import 'package:air_framework/air_framework.dart';
class CounterModule extends AppModule {
@override
String get id => 'counter';
@override
List<AirRoute> get routes => [
AirRoute(
path: '/counter',
builder: (context, state) => const CounterPage(),
),
];
@override
void onBind(AirDI di) {
// Register dependencies lazily
di.registerLazySingleton<CounterState>(() => CounterState());
}
}
2. Define State #
Use the @GenerateState annotation to magically generate reactive Flows and Pulses.
Simply modify fields like a standard Dart class (e.g. count++), and the framework automatically detects the change and updates only the widgets listening to that value. No boilerplate, no notifyListeners()βjust pure logic.
import 'package:air_framework/air_framework.dart';
part 'state.air.g.dart';
@GenerateState('counter')
class CounterState extends _CounterState {
// Private fields become reactive StateFlows
int _count = 0;
// Public methods become dispatchable Pulses
@override
void increment() {
count++;
}
}
3. Build Reactive UI #
Use AirView to listen to state changes efficiently. It automatically tracks which flows are accessed and rebuilds only when necessary.
class CounterPage extends StatelessWidget {
@override
Widget build(BuildContext context) {
return Scaffold(
body: Center(
child: AirView((context) {
// Auto-subscribes to 'count'
return Text('Count: ${CounterFlows.count.value}');
}),
),
floatingActionButton: FloatingActionButton(
// Triggers the 'increment' pulse
onPressed: () => CounterPulses.increment.pulse(null),
child: const Icon(Icons.add),
),
);
}
}
4. Initialize Your App #
Register your modules in main.dart.
void main() async {
WidgetsFlutterBinding.ensureInitialized();
// 1. Configure Air State
configureAirState();
// 2. Register Adapters (infrastructure β BEFORE modules)
final adapters = AdapterManager();
await adapters.register(DioAdapter(baseUrl: 'https://api.example.com'));
// 3. Register Modules (features β can use adapter services)
await ModuleManager().register(CounterModule());
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp.router(
title: 'Air App',
routerConfig: AirRouter().router,
);
}
}
π Adapters #
Adapters are headless service integrations. Unlike modules, they have no routes or UI β they register infrastructure services (HTTP clients, error tracking, analytics) in AirDI for modules to consume.
class SentryAdapter extends AirAdapter {
@override
String get id => 'sentry';
@override
void onBind(AirDI di) {
super.onBind(di);
// Register the abstract contract, not the concrete class
di.registerLazySingleton<ErrorReporter>(() => SentryReporter());
}
}
Key rule: every adapter must expose an abstract contract so modules never couple to a specific library.
lib/adapters/<service>/
βββ contracts/
β βββ <service>_client.dart β abstract interface
β βββ <service>_response.dart
βββ <service>_adapter.dart β AirAdapter subclass
βββ <service>_impl.dart β concrete implementation
Generate with the CLI: air g adapter sentry
π§ CLI Tools #
The Air CLI allows you to scaffold modules and generate state files instantly.
# Create a new project
air create my_app --template=starter
# Generate a new module
air generate module inventory
# Generate an adapter
air generate adapter sentry
# Generate state code
air generate state cart --module=inventory
π Related Packages #
| Package | Description |
|---|---|
| air_cli | Command-line scaffolding tool |
| air_state | Core reactive state package |
| air_generator | Build runner code generation |
π€ Contributing #
Contributions are welcome! Please read our contributing guidelines first.
π License #
This project is licensed under the MIT License - see the LICENSE file for details.
π Documentation #
For the full documentation, guides, and API reference visit:
Made by Andrey D. Araya