---
title: The uptime monitoring app you install from the browser
description: An uptime monitoring app with no app store: install WatchFor from the browser on iPhone or Android, get incident push and act on alerts from anywhere.
canonical: https://watchfor.io/blog/uptime-monitoring-app-pwa
---

# The uptime monitoring app you install from the browser

2026-10-19 · WatchFor Team · Monitoring · monitoring, uptime, incidents, on-call

An uptime monitoring app with no app store: install WatchFor from the browser on iPhone or Android, get incident push and act on alerts from anywhere.

It's 18:40 and you're at the school gate. The phone buzzes: **Payments API is
down**. The laptop is at home, twenty minutes away. You have two questions,
and they're the same two questions everybody has: *is it real*, and *is
anyone on it*?

That moment is why we built WatchFor's phone experience the way we did. Not a
companion app that shows a red dot and tells you to go find a computer, but
the whole dashboard, laid out for a thumb, and installable as an **uptime
monitoring app** straight from the browser. No app store, no separate login
system, nothing to keep in sync.

This post walks through what that looks like when something actually breaks,
how to install it on Android and iPhone, where an installed web app (a PWA)
is honestly worse than a native app, and what we're doing about that.

## What you can do from the phone when an alert lands

Tap the notification and you land on the incident in the right organization,
not on a home screen you have to dig out of. From there:

- **See whether it's real.** WatchFor opens an incident only after a failure
  is confirmed, from more than one location or by a repeat check. The
  incident page shows which locations confirmed it and when.
- **See why.** The root cause block says what happened in plain words, the
  diagnosis, what was expected and what was detected, here a `500` where the
  check expected `2xx` or `3xx`.
- **Take it.** Acknowledge pins your name to the incident so the rest of the
  team, and the escalation policy, know someone is on it. Resolve sits next to
  it in a bar that stays above the navigation while you scroll.

![Three iPhone screens from the Acme demo organization: the dashboard with one incident and an Acknowledge button, the Payments API incident acknowledged with its activity timeline, and the root cause analysis showing expected HTTP status 2xx or 3xx and detected status 500](/blog/uptime-monitoring-app-pwa-alert.webp)

The rest of the dashboard is there too, because it is the same dashboard. A
few things people do from the phone more than they expected to:

- **Run a check now** after a deploy or a fix, instead of waiting for the next
  scheduled run. Run now and Pause stay pinned at the bottom of every monitor.
- **Check who's on call** before you escalate to the wrong person.
- **Look at the public status page** your customers are looking at, to see
  whether it already says what you think it says.
- **Change routing in a hurry.** Mute a noisy Slack channel, add a contact,
  swap an on-call shift, with the same roles and permissions as on the
  desktop.

![Three iPhone screens in light mode: a website monitor's response time chart with Run now and Pause pinned at the bottom, the on-call schedule showing who is on call until when, and the Acme public status page with all systems operational](/blog/uptime-monitoring-app-pwa-actions.webp)

Charts redraw for the screen width with readable axes and a range brush, and
both light and dark themes are designed rather than inverted. If your
organization has the in-app AI Agent switched on (it's in early access), it
works on the phone as well: ask why a check keeps failing and it answers from
your own runs.

## Push notifications: what works where

Push is per device. You turn it on under **Settings → Notifications → Push
notifications** on each phone or computer that should get it. A confirmed
incident arrives with the monitor and what went wrong; when it resolves, the
resolved notification replaces the first one, so your lock screen doesn't
fill up with stale alarms.

| Where | Push | Acknowledge from the notification |
| --- | --- | --- |
| Android | Yes | Yes |
| iPhone and iPad, installed app, iOS/iPadOS 16.4+ | Yes | No, open the app |
| Desktop Chrome and Edge | Yes | Yes |
| Desktop Firefox and Safari | Yes | No, open the app |

The Acknowledge button acknowledges as you without opening anything, and the
activity log records it exactly like an acknowledgement made in the
dashboard.

One thing push is not: a replacement for your alert channels. It's personal,
it lives on one device, and a phone on silent is a phone on silent. Keep
email, Slack, Teams, Telegram, PagerDuty or webhooks, and on-call paging, as
the channels your team relies on, and treat push as the fast lane on top. The
details are in the [push notification docs](/docs/organization#push-notifications).

## How to install the monitoring app on Android and iPhone

Installing takes about ten seconds and needs nothing but the browser you
already have. From your second visit, phones also show a small **Install
WatchFor** card on the dashboard that walks you through it.

**Android** (Chrome, Edge or Samsung Internet)

1. Open [watchfor.io](/) and sign in.
2. Tap **Install app** on the dashboard card, or in your avatar menu.
3. Tap **Install**.

In Firefox for Android, open the **⋮** menu and choose **Install**.

**iPhone and iPad**

1. Open WatchFor in Safari.
2. Tap **Share**, then **Add to Home Screen**, then **Add**.
3. Open WatchFor from the Home Screen and sign in once.
4. Turn on push under Settings → Notifications → Push notifications.

Chrome and Edge on iOS 16.4 or later have Add to Home Screen under Share too.
Push on iPhone only works from the installed app, not from a Safari tab, so
step 3 matters.

![Two phones in dark mode: the Install WatchFor card on an iPhone dashboard with the Share and Add to Home Screen steps, and the WatchFor dashboard in Chrome on an Android phone](/blog/uptime-monitoring-app-pwa-install.webp)

The same works on a laptop. In Chrome or Edge, click the install icon at the
right end of the address bar; on a Mac with Safari (Sonoma or later), choose
File → Add to Dock. WatchFor then gets its own window, its own taskbar or
Dock icon, and desktop push, which is handy if your browser has forty tabs
and the dashboard is always the one you can't find.

![The installed WatchFor desktop app in its own window on a Linux desktop, showing the Acme organization's dashboard: all clear, healthy share of monitors and hosts, and plan usage](/blog/uptime-monitoring-app-pwa-desktop.webp)

## Why a PWA is a good monitoring app today

A progressive web app is a website the browser lets you install. For a
monitoring tool, that turns out to be a better trade than it sounds.

- **Nothing to update.** When we ship a fix to the dashboard, the installed
  app has it on the next open. There's no store review between a bug fix and
  your phone, and no "please update to see this incident type".
- **Nothing missing.** Every page you use on the desktop, from monitors and
  hosts to on-call, status pages, reports and settings, works at phone width.
  It isn't a cut-down companion with a list of things it can't do.
- **Same account, same data, same permissions.** There's no second sign-in
  system and no mobile API with its own quirks. What you see on the phone is
  what your teammate sees on their laptop.
- **iPhone and Android from day one.** One app, both platforms, the same
  week.
- **Small.** No download to speak of, no storage to clear.

## Where a PWA falls short of a native app

We'd rather you hear the limits from us than discover them at 3 a.m.

- **It needs a connection.** Like the dashboard, the installed app shows live
  data and doesn't work offline. Without a network it shows a short notice
  and reloads by itself when you're back online.
- **iPhone push has conditions.** It needs iOS or iPadOS 16.4 or later and
  the installed app, and iPhone notifications have no Acknowledge button:
  tapping one opens the incident instead.
- **No store listing.** If your company only allows apps from a managed app
  store, a browser-installed app may not be an option for you.
- **The platform decides some things.** How long a background notification
  can take to arrive, how notifications group, what a long-press shows: on
  the web those are the browser's choices, not ours.

## What's next: the native Android app

For the cases above, we're building a native Android app. It works in our lab
today and is in testing: home with what needs a person, one-tap Acknowledge,
monitors, hosts, incidents with root cause, on-call and quick create. We'll
ship it when it's ready, not before; if you'd like to try it early, there's a
beta sign-up on the [Android app page](/mobile-app).

Until then, the installed web app isn't a stopgap. It's the full product,
and it's what we use ourselves when the alert finds us away from the desk.
Everything above, with real screens on both platforms, is on the
[mobile page](/mobile).

## FAQ

**Is there a WatchFor app for iPhone and Android?**
Yes. WatchFor installs as an app straight from the browser on Android, iPhone
and iPad, without an app store, and receives incident push notifications. A
native Android app is in testing.

**Is the mobile version missing features?**
No. It's the same dashboard with the same roles and permissions: monitors,
hosts, incidents, on-call, status pages, reports, channels and settings all
work on a phone.

**Do push notifications work on iPhone?**
Yes, on iOS and iPadOS 16.4 or later from the installed app. Add WatchFor to
the Home Screen, open it from there and turn push on under Settings →
Notifications → Push notifications.

**Does it cost extra?**
No. The phone and the installed app are part of every plan, including Free.
See [pricing](/pricing) for what each plan includes.

---

Canonical page: https://watchfor.io/blog/uptime-monitoring-app-pwa · All articles: https://watchfor.io/blog/all.md · Site guide: https://watchfor.io/llms.txt