reactive_orm #

|

⚠️ Note: reactive_orm stands for a Reactive Object–Relationship Model.
It is not a database ORM.
It is a lightweight, field-level state management solution for Flutter UI, inspired by ORM-style modeling of objects and relationships — fully in-memory and UI-focused.

🎬 Demo #

✨ Core Philosophy #

• Models are plain Dart objects
• State changes happen via normal field mutation
• UI reacts automatically, with optional field-specific reactivity
• No ChangeNotifier, providers, streams, or extra boilerplate
• Supports object-wise, field-wise, and nested reactivity
• ORM-inspired design:
  • Objects represent application state
  • Relationships define propagation (Many → One, Many ↔ Many)
  • Reactivity keeps the UI in sync

✨ Features #

• ✅ Reactive models with automatic UI updates
• ✅ Object-wise reactivity (entire model rebuilds)
• ✅ Field-wise reactivity (only selected fields rebuild)
• ✅ Nested & shared models supported
• ✅ Many → One and Many ↔ Many relationships
• ✅ Multiple widgets can listen to the same model
• ✅ Minimal boilerplate
• ✅ ORM-style mental model (Objects + Relationships)

🚀 Getting Started #

Installation #

dependencies:
  reactive_orm: <latest_version>

🧩 Basic Usage #

1️⃣ Create a Reactive Model import 'package:reactive_orm/reactive_orm.dart';

class Task extends ReactiveModel { String _title; bool _completed = false; String _status = "Idle";

Task({required String title}) : _title = title;

String get title => _title; set title(String value) { if (_title != value) { _title = value; notifyListeners('title'); } }

bool get completed => _completed; set completed(bool value) { if (_completed != value) { _completed = value; notifyListeners('completed'); } }

String get status => _status; set status(String value) { if (_status != value) { _status = value; notifyListeners('status'); } } }

2️⃣ Object-wise Reactivity final task = Task(title: "Object-wise");

ReactiveBuilder

3️⃣ Field-wise Reactivity final task = Task(title: "Field-wise");

ReactiveBuilder

🔗 Relationship Patterns #

Many → One (Aggregation) class Dashboard extends ReactiveModel { final List

final dashboard = Dashboard([task1, task2]);

ReactiveBuilder

Many ↔ Many (Shared Models) class Group extends ReactiveModel { final String name; final List

Group({required this.name, required this.tasks}) { for (final task in tasks) addNested(task); } }

🧠 How It Works #

• Models extend ReactiveModel.
• Field setters call notifyListeners(fieldName) when the value changes.
• ReactiveBuilder widgets listen to:
• Whole model (object-wise)
• Specific fields (field-wise)
• Nested models propagate changes upward automatically.
• Widgets rebuild safely, respecting Flutter lifecycle.

🛣 Roadmap #

• Batch updates / transactions
• Async persistence hooks
• Database adapters (optional)
• DevTools / debug inspector
• Optional code generation

🧪 Status #

• Version: 1.0.0
• Stability: Stable
• Focus: Reactive domain models & scalable state management

📌 Summary #

reactive_orm is ideal for:

• Clean Dart models with fine-grained reactivity
• A Reactive Object–Relationship Model for UI state
• Object-wise and field-wise rebuild control
• Nested and shared models without manual wiring
• Minimal boilerplate with a clear mental model
• A lightweight yet scalable state management solution for Flutter apps

🆚 Comparison #

In More Brief -------------- #

Provider vs reactive_orm #

BLoC vs reactive_orm #

Riverpod vs reactive_orm #

MobX vs reactive_orm #