Add named geographic region event sources #1

New issue

Open

opened 2026-09-16 01:09:38 +02:00 by morten-olsen · 0 comments

morten-olsen commented

2026-09-16 01:09:38 +02:00

Owner

Context

Geographic regions are visible as unavailable trigger definitions. Android's platform geofencing API is circular, while the requested product model includes geographic boxes.

Scope

Define explicit enter/exit delivery semantics for named regions.
Decide how rectangular regions map to platform capabilities without pretending Android provides native box geofences.
Design foreground/background location permission behavior and availability states.
Reconcile registrations when workflows, sources, permissions, or device state change.

Acceptance

Users can create, edit, subscribe to, and safely delete named region sources.
Region geometry and approximation semantics are visible to users.
Background delivery and permission failures are explicit.
Disabled/deleted workflows leave no stale geofence registrations.

## Context Geographic regions are visible as unavailable trigger definitions. Android's platform geofencing API is circular, while the requested product model includes geographic boxes. ## Scope - Define explicit enter/exit delivery semantics for named regions. - Decide how rectangular regions map to platform capabilities without pretending Android provides native box geofences. - Design foreground/background location permission behavior and availability states. - Reconcile registrations when workflows, sources, permissions, or device state change. ## Acceptance - Users can create, edit, subscribe to, and safely delete named region sources. - Region geometry and approximation semantics are visible to users. - Background delivery and permission failures are explicit. - Disabled/deleted workflows leave no stale geofence registrations.

morten-olsen referenced this issue

2026-09-16 21:55:05 +02:00

Broaden platform action and trigger coverage #22

morten-olsen added the

feature

label

2026-09-17 08:19:57 +02:00