For many developers in Southeast Asia and Latin America, the smartphone is the primary computing device. You're on mobile during your commute, during client meetings, and whenever something breaks at 11 PM.
Mobile-first uptime monitoring isn't about having a nice app (though that helps). It's about getting the right alert to the right place so you can respond before your clients do.
Here's how to set up monitoring that works the way you actually work — from your phone.
The Alert Hierarchy for Mobile-First Developers
Not all alert channels behave the same on a mobile device:
WhatsApp: Interrupts immediately. Default notifications on WhatsApp bypass most Do Not Disturb settings on Android. Shows on your lock screen. You see it even if you're not actively looking.
Telegram: Similar to WhatsApp. Good for teams where multiple people need to see alerts in a shared channel. Some developers set up a dedicated monitoring Telegram group with themselves and their team.
Push notifications (ndelog app): Sent directly to the ndelog mobile app. Useful for checking monitor status, acknowledging alerts, and reviewing history from your phone. On iOS, you can configure priority notifications to bypass Focus modes.
Email: Appears as a badge on your mail app. Easy to miss. Fine for non-urgent summaries; bad for active downtime response.
For active downtime — you need to be notified and respond — WhatsApp or Telegram is the answer. Email is for reports.
Setting Up Mobile Monitoring with ndelog
Step 1: Download the ndelog app Available on iOS and Android. Log in with your account credentials.
Step 2: Enable push notifications In the app, go to Settings → Notifications and enable push alerts. On iOS, grant notification permissions when prompted. You can register up to 10 devices — useful if you use multiple phones or share monitoring duties with a colleague.
Step 3: Configure per-monitor push mute Not every monitor needs to wake you up. For a staging environment or a non-critical service, you can mute push notifications on that specific monitor while still logging incidents. The mute is per-monitor — your production monitors still interrupt.
Step 4: Add WhatsApp as a backup alert channel Push notifications depend on your device being connected and the app being installed. WhatsApp alerts arrive independently of the ndelog app. Set up WhatsApp as a secondary channel so you get both — the push from the app and the WhatsApp as a redundant path.
Checking Status from Your Phone
The ndelog mobile app lets you:
- See current status of all monitors at a glance (green/red status grid)
- View response time graphs per monitor
- Read incident history and duration
- Access your public status page URLs to share with clients
- Add or pause monitors (basic management)
For the full dashboard — creating monitors, editing alert routing, generating reports — you'll want the web interface. The mobile app is optimized for status checks and alert response, not setup.
The On-Call Reality for Solo Developers
If you're the only person monitoring your clients' sites, "on-call" is permanent. You don't have a rotation. When something breaks at 2 AM, it's your problem.
Setting up WhatsApp alerts properly means accepting that your phone will buzz when sites go down — even at night. The alternative (finding out at 9 AM when a client calls) is worse.
Some practical boundaries:
- Set WhatsApp to priority/starred contacts for the ndelog sender number so it cuts through Do Not Disturb
- Use per-monitor muting to suppress staging alerts overnight
- Consider a dedicated low-cost SIM/number for monitoring alerts if you want physical separation from personal WhatsApp
The Multi-Device Setup
If you have a team member who also needs alerts:
- Add their WhatsApp number as a second alert channel (Warden supports up to 3 WhatsApp numbers)
- They install the ndelog app on their phone and you add their device
- For incidents they handle, they can acknowledge from the app
For a two-person freelance team, this covers the weekend/vacation handoff problem without building an on-call rotation system.