Documentation
Mobile apps
The iOS and Android apps exist for one moment: 3 am, phone on silent, something broken. Everything in them is built around making that notification heard and letting you act on it in one tap.
Installing and signing in
Sign in with your email address and the code it receives, the same as the console. Accounts and organizations are created on the web, at app.igniteops.io; the app signs in to an existing account. On the first launch the app asks for notification permission, and on iOS for permission to send critical alerts, which is a separate prompt. Say yes to both.
Alerts that sound through silent mode
A normal push notification is silent on a silenced phone, which makes it useless as a pager. The two platforms solve this differently, and the app does what each one needs.
| iOS | Android | |
|---|---|---|
| How | Apple granted IgniteOps the critical alerts entitlement. The alert is delivered as a critical notification, which the system sounds at a set volume through silent mode and every Focus mode. | A few seconds before the alert, the app receives a silent wake-up message. It lifts Do Not Disturb, sets the ringer to normal and raises the volume, so the notification sounds with its own channel sound. Afterwards it puts everything back. |
| What you grant | The "Allow critical alerts" prompt on first launch (Settings → Notifications → IgniteOps later). | "Do Not Disturb access" for IgniteOps, from the app’s Settings. Android refuses to un-silence a phone for any app without it. |
| If you do not grant it | Alerts arrive as normal notifications and stay silent on silent. | The same. The app shows a warning on its Settings screen while the access is missing. |
| Gotcha | None known. | Reinstalling the app silently revokes the grant. Check it after a reinstall. |
The app plays no sound of its own on either platform. The notification does.
Acting from the notification
The notification carries Acknowledge and Close buttons, so the escalation can be stopped from the lock screen without opening the app. Tapping the notification opens the alert, with its description, its timeline, its properties and the same actions.
What is in the app
- Home: who is on call right now across your teams, the open and acknowledged counts, the latest alerts.
- Alerts: the list with filters and search, acknowledge and close in one tap, and Create alert for any team, routed and escalated like one from a webhook.
- On-call: the schedules of your teams, who is on call on each and the next hand-over.
- Teams: the teams you belong to and their members.
- Settings: your notification methods (order, delays, adding and verifying a phone number), the app lock with biometrics and its grace period, light and dark theme, and account deletion with its 30-day grace period.
How a phone stays registered
A phone registers itself as a push device the first time you sign in on it, under a stable identifier, and re-registers whenever the push token changes. Only an explicit sign out removes the registration: an expired session keeps the phone registered, so the person on call is still paged even if they have not opened the app in weeks. You can see, rename, test and remove your phones from Account → Notifications in the console.
What stays in the console
Creating an organization, billing and the plan, inviting members, and editing schedules, escalation policies, routing rules and integration keys are done in the web console. The app is for being paged, acting on alerts and seeing who is on call. Both share the same account, the same organizations and the same notification settings.
Checked against the product on November 8, 2026.