Mobile app and push
The panel can be installed as an app on phones and computers, and it sends monitor alerts as push notifications to browsers and installed apps. Push is sent by the platform itself (Web Push with VAPID keys); no third-party push service or account is needed. The administrator can also download ready-made Android and iOS projects to publish in the app stores.
Install the web app
The site is a Progressive Web App (PWA): it has a manifest (/manifest.webmanifest), a service worker (/sw.js) and icons drawn in the brand colour.
- Chrome, Edge, Android: an Install app button appears in the panel when the browser offers installation (also on Devices & push), or use the browser menu.
- iPhone and iPad: in Safari tap Share → Add to Home Screen.
The installed app opens the panel (/app by default) in its own window and offers shortcuts to Monitors, Incidents and Devices & push. Panel pages you opened are kept for offline use; without a connection a saved copy or an offline page is shown. Signing out clears the saved pages.
Browsers allow installation, service workers and push only on https (and on localhost for testing).
Enable push on a device
Open Devices & push (/app/devices, in the panel menu above Settings).
- Optionally type a Device name ("My phone").
- Press Enable push on this device and allow notifications when the browser asks.
- Press Send test next to the device in Your devices to check delivery.
Turn off on this device removes the subscription. The badge shows the state: On, Off, Blocked (notifications denied in the browser's site settings: allow them and reload) or Not supported.
On iPhone and iPad push works only in the installed web app (iOS 16.4 or newer): add it to the home screen, open it from there and enable push inside it.
The device list shows every browser and app device of your account with type, when it was added, the last successful delivery and the last error. You can rename or remove a device. Devices belong to your user, not to the organisation. Each user can have 20 devices (the administrator may change this); adding one more drops the oldest. A device that the push service reports as gone (HTTP 404/410) is removed automatically; one that fails 20 times in a row is switched off.
The push alert channel
Devices only ring when an alert channel sends to them:
- Enable push on every browser or phone that should ring.
- Under Alert channels add a channel of the type Browser & app push. Its audience is
me(the devices of the channel's owner) ororg(the devices of every active team member). - Pick that channel on your monitors, or make it a default channel.
Down and escalation alerts are sent with high urgency and stay on screen until dismissed; repeated alerts for the same monitor replace each other. Tapping a notification opens its link in the panel. The channel reports "Sent to N of M devices"; when nobody has push switched on, the delivery fails with "No device has push notifications switched on". See Alerts.
The dashboard
The dashboard is made of cards: Overview, Needs attention, Recent incidents, Recent alerts, SSL certificates expiring, Domains expiring, Servers, Plan usage, Activity and Push devices (how many of your browsers and app devices receive push, and how many have delivery errors).
Press Customise to drag the cards into another order (or use the arrow buttons), untick a card to hide it, then Save layout. Reset to default brings back the original layout. The layout is saved per user. Cards added by a later update appear at the end.
Android and iOS apps (administrator)
Admin → Mobile apps builds complete app projects with the site's name, address, colours and icons filled in. Building and publishing happen on your own computer with the vendors' free tools and your own developer accounts.
Settings
| Field | Meaning |
|---|---|
| App name | Blank = the site name (max 50 characters) |
| Short name | Under the home-screen icon, max 12 characters |
| Theme colour / Background colour | Status/title bar and splash screen. Default theme colour: the brand colour |
| Start page | Path the apps open, default app |
| App icon | Square PNG, JPG or WebP, 512 × 512 or larger. Blank = the brand mark in the theme colour |
| Android package id | Like com.example.monitor; cannot change after the app is published on Google Play. Default: the site's host reversed plus .app |
| iOS bundle id | Default: the Android package id |
| Version name, Version code / build number | Raise the code for every store upload |
| Apple team ID | 10 letters and digits; enables universal links |
| Google Play address | https://play.google.com/store/apps/details?id=..., only once the app is live; browsers then point Android users to it |
| Android signing SHA-256 fingerprints | One per line (AB:CD:..., 32 pairs) |
| Push contact | The VAPID contact sent to push services; blank = the contact e-mail |
| Push message lifetime (seconds) | How long a push service keeps a message for an offline device (default 86400) |
| Devices per user | 1–100 (default 20) |
| Allow push endpoints on http and local addresses | Testing only |
The page also shows the manifest, service worker, icons, the VAPID public key (the private key is stored encrypted) and whether Digital Asset Links and iOS universal links are published. Make new VAPID keys removes every browser subscription; users must enable push again.
When the Android package id and a fingerprint are set, the site publishes /.well-known/assetlinks.json; with the Apple team ID and bundle id it publishes /.well-known/apple-app-site-association.
Build the Android app
Press Android project (ZIP). The project is a Trusted Web Activity: the panel runs full screen in Chrome's engine, shows the site's push alerts as the app's notifications, and falls back to a built-in WebView on phones without a suitable browser.
- Install Android Studio and open the unzipped folder with File → Open. The first sync downloads Gradle and the libraries.
- Run it on an emulator or phone (Run → Run 'app').
- Build → Generate Signed App Bundle / APK and create an upload keystore. Keep it safe: every update must be signed with it.
- Get the SHA-256 fingerprint and paste it on Admin → Mobile apps; until then the app shows a small URL bar. With Play App Signing also add the fingerprint from Play Console → Setup → App integrity.
keytool -list -v -keystore upload.keystore -alias upload
- Upload the
.aabin Google Play Console, usestore-icon-512.pngfrom the ZIP as the store icon, fill in the listing and send it for review.
Build the iOS app
Press iOS project (ZIP). The project is a SwiftUI app around a WKWebView: pages of the site stay in the app, other links open in Safari, pull down to reload, and an offline screen offers "Try again". You need a Mac with Xcode 15 or newer.
brew install xcodegen
xcodegen
- Run
xcodegenin the unzipped folder; it writes the.xcodeprojfromproject.yml. Without XcodeGen, create a new iOS App project (SwiftUI) with the same bundle id and drag theAppfolder in. - Pick your team under Signing & Capabilities (or set the Apple team ID before downloading) and run it.
- Product → Archive → Distribute App → App Store Connect, then submit it for review.
The iOS app shell does not register for Apple push. iPhone users get push alerts from the installed web app (iOS 16.4+), as described above.
Native push tokens
Android (FCM) and iOS (APNs) tokens can be registered through the API and are listed on Devices & push, but the platform does not deliver to them: that needs the publisher's own Google/Apple push credentials. Alerts reach phones through Web Push.
Device API
The apps use the API with a token from API & webhooks; the scope read is enough, because the endpoints only touch the token user's own devices.
| Method | Path | Does |
|---|---|---|
GET | /api/v1/devices | The token user's devices, plus vapid_public_key |
POST | /api/v1/devices | Register a device: {"kind":"webpush","endpoint":"…","keys":{"p256dh":"…","auth":"…"}} or {"kind":"fcm","token":"…"} / {"kind":"apns","token":"…"}, optional name. 201 when new, 200 when the device already existed |
DELETE | /api/v1/devices/{id} | Remove a device |
GET | /api/v1/me/summary | Numbers for a home-screen widget |
/me/summary answers the organisation, an overall state (down, degraded, up or empty), monitor counts (total, up, down, degraded, paused, pending), server counts (total, online, offline), open incidents, 30-day uptime, average response time, up to 10 monitors that are down or degraded (problems), the number of unread notifications and the dashboard link.
curl -H "Authorization: Bearer <token>" https://your-monitor.example/api/v1/me/summary
Push endpoints must be https and pass the SSRF guard; key material is never returned by the API.
একটি ক্লিক আমাদের এই ডকস উন্নত করতে সাহায্য করে।

