[Ambient] iOS gap analysis: BT/WiFi inaccessible; location-only path #120

New issue

Closed

opened 2026-06-29 19:24:08 +00:00 by Mark · 1 comment

Mark commented

2026-06-29 19:24:08 +00:00

Owner

Parent: #108

Problem

iOS gives no public Bluetooth scan API and no third-party WiFi scan API. Only geofences (CLCircularRegion) work for ambient detection. Need a documented matrix + an iOS-specific implementation path.

Scope

Document what's accessible on iOS: Capacitor Geolocation (while-in-use), significant-location-change, geofence monitoring
Disable / hide BT and WiFi source toggles on iOS in the Settings UI from #
iOS implementation of location-based ambient detection using CLLocationManager

Out of scope

iOS-call / SMS passive ingestion (separate issue if wanted; same OS-level barriers as Android require separate scope)

## Parent: #108 ## Problem iOS gives no public Bluetooth scan API and no third-party WiFi scan API. Only geofences (`CLCircularRegion`) work for ambient detection. Need a documented matrix + an iOS-specific implementation path. ## Scope - Document what's accessible on iOS: Capacitor Geolocation (while-in-use), significant-location-change, geofence monitoring - Disable / hide BT and WiFi source toggles on iOS in the Settings UI from # - iOS implementation of location-based ambient detection using CLLocationManager ## Out of scope - iOS-call / SMS passive ingestion (separate issue if wanted; same OS-level barriers as Android require separate scope)

Mark added the

labels

2026-06-29 19:24:08 +00:00

Mark commented

2026-06-29 20:38:06 +00:00

Author

Owner

What the human call is

iOS ambient has no public BT/WiFi scan APIs. The shape is forced: geofence-only. Decisions needed:

Surface same suggestions experience as Android? Or iOS-flavored (passive, no rec-to-confirm prompt)?
Capacitor Geolocation vs Apple's CoreLocation directly?
Geofence count cap (Apple allows 20 per app) — which people/places win a geofence?

Pick before dispatch.

## What the human call is iOS ambient has no public BT/WiFi scan APIs. The shape is forced: geofence-only. Decisions needed: 1. Surface same suggestions experience as Android? Or iOS-flavored (passive, no rec-to-confirm prompt)? 2. Capacitor Geolocation vs Apple's CoreLocation directly? 3. Geofence count cap (Apple allows 20 per app) — which people/places win a geofence? Pick before dispatch.

Mark referenced this issue

2026-07-01 22:14:48 +00:00

[Ambient] Back-end: location, BT, WiFi, calendar ingest + suggestion engine #108

Mark

2026-07-07 18:05:10 +00:00