rest / 20-20-20
Devices and browsers
Timing, push notifications and pause on lock have different requirements.
Open timerSupport at a glance
| Device and browser | Timer | System push | Pause on lock |
|---|---|---|---|
| Desktop Chrome / Edge | Yes | Permission required | Capable browser and permission |
| Mac Safari / Add to Dock | Yes | Depends on OS and browser | No |
| Desktop Firefox | Yes | Permission required | No |
| Android Chrome | Yes | Permission and background support | Not currently offered |
| iOS / iPadOS Home Screen app | Yes | 16.4+ and separate permission | No |
| Ordinary iPhone browser tab | In foreground | Use the Home Screen app | No |
Based on the current implementation and platform documentation, not tests on every physical device. Versions, enterprise policies and OS settings can change availability; check the app’s capability detection and notification test.
After installing on Mac
A Chrome or Edge installation still depends on that browser’s capabilities. Safari’s Add to Dock does not add lock detection. A standalone window is not a native app with extra system permissions.
Why iPhone says unavailable
Home Screen web apps can receive authorized push notifications, but iOS does not provide the Idle Detection capability rest uses for screen locking. Installing the app or changing browser does not guarantee that capability.
Requirements for pause on lock
Use a capable desktop browser, grant device-use detection, and keep the page running and online. Locking pauses the cloud timer; unlocking resumes the remaining time. A manually paused timer stays paused.
Ordinary inactivity and switching tabs do not pause it. Closing or freezing the browser, going offline or system sleep can prevent lock events reaching the cloud. Display power alone is not detected.
Platform references
Updated