Conventional in-app notification packages in Flutter force an architectural anti-pattern: they demand an active BuildContext, pollute widget trees, and bind the visual toast directly to the call site. When an event originates from a background isolate, a reactive state machine, or a network worker, finding a valid context or navigating modal overlays causes crashes, race conditions, or dropped notifications.
flutter_notification_queue (FNQ) enforces a clean architectural boundary between event generation and spatial rendering. An alert is declared as a pure data payload (AppNotification), routed through a typed channel, and triaged by a global controller. The engine handles spatial topology, gestures, priority preemption, and deck bundling entirely above the navigator stack.
01
Contextless Delivery
Trigger notifications directly from business logic, BLoCs, isolates, or network services without referencing BuildContext.
02
Spatial Topology & Gestures
Multi-zone positioning (topRight, bottomCenter, topLeft) with dynamic queue relocation and intent-driven gestures.
03
Priority Triage & Bundling
High-priority security or system alerts preempt the queue head immediately. High-frequency bursts collapse into aggregated decks.
Decoupled Architecture PipelineAppNotification pure event payload→NotificationChannel theme & behavior→NotificationQueue spatial viewport→NotificationScope overlay host