Instrument notifications: Android and iOS integration

Treat notifications as an optional feature

Displaying phone notifications requires riders to enable sharing and grant system permissions. Pairing and notification consent are separate flows; connecting a device should not enable sharing automatically.

Infinite Ride provides the phone-side controls and terminal SDK capabilities. Manufacturers integrate reception, layout and display behavior. Start by identifying the target phone platforms.

Android: the APP forwards new notifications

After notification access is granted, the APP sends newly received, system-permitted notifications to a verified terminal. The terminal returns the corresponding result and renders the content in its UI.

Test consent, first delivery, reconnection and explicit stopping. Background continuity depends on the phone OS and manufacturer policies. One successful foreground delivery does not establish support in every condition.

iOS: the terminal integrates ANCS

iOS shares notifications with compatible terminals through ANCS. The APP does not directly read notification bodies from other apps. The terminal needs an ANCS client implementation, system permission and a working subscription.

The SDK provides ANCS data handling; your team still adapts the terminal’s Bluetooth interfaces. Verify subscription, attribute retrieval and display separately rather than treating a capability declaration as a completed integration.

Validate stopping as well as receiving

• Does disabling sharing stop reception and display?
• Are APP and terminal state consistent after permission is revoked?
• Does reconnection respect the rider’s previous choice to enable or disable sharing?
• Does behavior after force-stop, reboot and platform-specific background restrictions match the product description?

Record results for each phone platform and target terminal before defining the supported notification feature set.

View APP capabilities · Assess notification integration