I built ScreenSky because a break timer that interrupts a call is easy to switch off and forget about. I also wanted a way to pick up my work again after a break. Those turned out to be two separate design problems.
A break timer has more than one decision to make
When a work interval ends, the obvious thing to do is show the break. The harder question is whether now is a good time. ScreenSky has a Smart Pause setting that can hold the timer when the microphone is in use, and you can configure how it behaves around selected apps or other activity. A microphone in use is a useful signal, but it can also mean recording or dictation. Treating that signal as a preference gives users control over which interruptions they want to avoid.
There is a separate case right before a break: you might be finishing a sentence. A warning countdown gives you time to wrap up, and typing detection can hold the final countdown while you are still typing. That gives the timer a way to defer a short interruption without treating ordinary typing as a reason to pause indefinitely.
What happens when the break ends?
ScreenSky can show your pending tasks during a break. The task board and notes are stored locally, and a keyboard shortcut makes it possible to capture the next step before changing apps. The aim is to have a concrete thing to return to when the break is over.
If you have built a desktop app with scheduled notifications, what signal turned out to be the most useful for deciding when to wait?
This post was prepared with AI assistance.
Top comments (0)