Omega Flutter

Appearance

Omega FlutterReactive, agent-based architecture

One event channel, typed intents, flows and agents — inspect, trace, and measure what matters.

Vision & why Omega
Get started
pub.dev package
Source
Observe & measure
Omega

Vision

Intent-first collaboration — flows orchestrate, agents handle IO, one shared channel.

OmegaChannel & events

Broadcast typed events, namespaces for modules, and optional contracts in debug — see the channel guide.

Flows & agents

OmegaFlow receives intents and events; OmegaAgent runs behaviors. The UI stays thin; business rules live outside widgets.

Tooling

omega CLI (create app, generate ecosystem, traces, optional Omi AI), inspector overlay or browser + VM Service, and time-travel traces.

Observability & statistics

See live channel traffic and flow snapshots, record sessions for replay, and map intent→expression latency — one architecture, measurable behavior.

Built to be watched, not guessed

Omega keeps one clear pipeline from UI to flows to agents. That means you can inspect what happened, replay it, and define statistics (throughput, response paths, flow state) without reverse‑engineering a forest of providers. Observability & statistics →

Example Omega observability dashboard Illustrative metrics: events by category, latency, rate, and flow states. Not live data. Omega observability Example only / build real charts from inspector, traces, or your telemetry 1. Channel events (1 min) 2. Intent to expression (ms) 38 52 24 15 Intents Agent Nav Other p50 12 ms p95 47 ms 3. Events per minute (session excerpt) start +10 min 4. Active flows (snapshot) auth / running shop / idle profile / sleeping Not live data / shows the kinds of views the Omega channel + flow model supports.

What each panel means ​

The figure is a layout example with placeholder numbers. In a real setup you would compute the same views from traces, inspector exports, or your own timers. For the full metrics story, see Observability & statistics.

  1. Channel events (1 min) — A count mix of everything that crossed the Omega channel in the last minute, grouped by rough kind: Intents (mostly UI → flow), Agent (agent / bus traffic you attribute to agents), Nav (navigate.* and related), and Other (everything else). Spikes in one bucket often point to a chatty widget, a loop, or a navigation storm.

  2. Intent to expression (ms) — Latency bands for “how long from handling an intent until the owning flow emits the next OmegaFlowExpression.” p50 is the typical case; p95 catches tail latency users still feel. This is the closest single chart to “Omega felt speed” for the screen.

  3. Events per minute (session excerpt) — A time series of channel throughput (events per minute) over a short window (here labeled start → +10 min). Use it to spot bursts, plateaus, or regressions after a release.

  4. Active flows (snapshot) — A point-in-time row of flows that exist in the session: each pill is a flow name plus a coarse state (for example running vs idle vs sleeping). It answers “what is alive right now?” — useful next to the inspector’s flow list.

By the numbers (why teams reach for it) ​

One channelA single OmegaChannel coordinates the app: every important message has a name and a place in the timeline.
Every flow, one snapshotThe inspector summarizes all registered flows — state and last expression — so “who is running?” is never a mystery.
30 recent events (default)The inspector keeps a rolling window of channel events in view so you spot storms, duplicates, and ordering bugs quickly.
Ordered sessionsTime‑travel recording preserves event order for offline analysis or CLI tooling — your first “statistics export” is often a trace file.

What is this site? ​

Structured documentation for the omega_architecture package (Flutter): same role as official Flutter docs — Get started → Topics → Advanced → Tools → API reference. Use the left sidebar on any guide page to move between sections.

Documentation hub ​

Get started ​

Getting startedInstall CLI, new app, existing app, learning path
Core conceptsGlossary: channel, intent, flow, agent, expressions
Data flowUI → manager → flow → channel → agent → UI
omega_setup.dartComposition, cold start, namespaces, handlers
Example appRunnable auth + modules in example/

Understand & decide ​

Vision & why OmegaWhen Omega fits your team
Total architectureOne diagram of the whole stack
Omega vs BLoC / RiverpodHonest trade-offs
Observability & statisticsInspector, traces, metrics mindset, intent→expression

Build features ​

Channel & eventsBus, namespaces, typed names, dispose
Intents, flows & managerRouting intents, flow lifecycle
Agents & behaviorsSide effects, onAction, stateful agents
Navigation & routesnavigate.*, typed routes
Flutter widgetsOmegaScope, flow/agent builders, inspector, RootHandler

Advanced ​

ContractsFlow/agent contracts in debug
Time travel & tracesRecord, replay, omega trace, AI explain
Offline-first intentsQueued intents when offline

Tools & reference ​

Omega CLIAll commands including omega ai
Inspector & VM ServiceOverlay, launcher, browser + VM
TestingUnit-test flows and agents
API referenceMap to pub.dev API docs
Repository layoutlib/, example/, docs/, CI

The hosted Inspector HTML (VM Service) page is the URL the CLI and OmegaInspectorServer open; a copy also ships with this site at Inspector HTML.

The README on GitHub has a short pitch and badges.

Author ​

Omega is developed by Yeferson Segura (mobile · web · product-oriented software). More context: About the author.