Devices without GMS
Devices without Google Services can receive alerts. Tested on an AOSP emulator without Google Services, including screen-off delivery and recovery of queued events after a restart.
Architecture
The app connects directly to your server. Google Services and a messenger are optional. The phone needs HTTPS access to the installation; a private network may require a VPN.
A common Android push notification path goes through Google’s infrastructure: the app registers with FCM, your server sends Google a message, and Google wakes the phone. That path depends on Google Services availability and device settings.
Acktide uses a different path. The Android app runs a foreground service and keeps a WebSocket connection directly to your installation. The server that receives the Alertmanager event delivers it to the device itself. There is no push delivery intermediary between your server and the phone.
FCM is still available as an optional addition. If you have a Firebase configuration and want to use it, enable it in the settings. Acktide does not require it.
Devices without Google Services can receive alerts. Tested on an AOSP emulator without Google Services, including screen-off delivery and recovery of queued events after a restart.
With monitoring and Acktide inside your network and the phone connected directly, you control the data path. Leave optional FCM and external integrations disabled if they do not meet your network requirements.
Acktide handles delivery and acknowledgments. Your team operates the server, database and network access to the installation.
Background delivery requires Android permissions and network access. Check both on the phones your team uses.