A timer that shouldn't interrupt you: permissions, prompts

Round two, phone face-down on the bench, hands on the bell. The screen lights up. Not a call, not a message. The timer would like you to consider turning on Bluetooth.

“I do not want to turn on Bluetooth… I cannot find any setting to disable the attempts to connect. this interrupts every workout session” (one-star review of an interval timer, September)

The detail worth sitting on is “attempts”, plural. The app asked more than once, mid-session, and when the reviewer went looking for a way to make it stop, there was none to find. Nothing was broken. The timer worked exactly as designed, and the design included interrupting people.

Two kinds of interruption

A call mid-round, an app switch that freezes the clock, the phone’s battery settings quietly killing the session in the background: those interruptions come from the world, and the call mid-workout has its own writeup. This article is about the other kind, where the timer itself is the source. A permission dialog in the middle of a round. A sign-in wall between the install screen and the first interval. And in the quietest case, an app that needs a moment just to become a timer.

The distinction matters because of who is at fault. When the phone rings, the timer is a bystander with a hard job. When the timer asks about Bluetooth mid-set, a person chose that moment on purpose, which means a person could have chosen differently. An interruption by the world is Tuesday. An interruption by design is what turns a user into a reviewer.

The prompts that follow you into the gym

Every permission prompt has a reason behind it. Watch pairing wants Bluetooth, and so do heart-rate straps, which at least serve you. Advertising kits want to scan for nearby beacons because somebody upstairs wants to know which gym you go to. Each prompt is somebody’s feature or somebody’s metric. None of them is counting your rounds.

The problem is the timing, and the timing is curable. An app that knows enough to beep in exact seconds knows a workout is running, because it is the one running it. Asking a person under a bar to make a pairing decision is not a technical necessity. It is a priority, visible in the product.

The same family includes the front door some apps put up: a launch video that plays every single time, then a sign-in with Gmail or Apple, and the toggle meant to skip the video leads to a pricing page. A longtime user of that app put the feeling in one line: “something about it just sat wrong with me.” Another verdict from the same pile of complaints: “asking me to make an account just to do an AMRAP.” The account serves the company’s funnel. The beeps are the product.

The cold start tax

The quiet version of the same problem is an app that takes its time becoming itself. You tap, the logo appears, and then you wait. From late August, about a workout timer after an update: “Have to restart app a billion Times before it actually lets you use it.”

The tax lands exactly where a timer cannot afford it. The whole point of the thing is that the gap between deciding to train and training is short, and a rest period, one of the four numbers a session is built from, is measured in tens of seconds. A timer that burns half of one just opening has already failed the easiest part of its job.

The slowness was shipped, and that is the part that stings. The app opened fine when you installed it. Then a release went out, with a new onboarding flow or a network call that waits for a server before showing anything, and the open got slower. What you experience as “it got slow” is usually a choice somebody made in a changelog. If a timer you trusted in spring takes a running start in fall, read the newest reviews instead of the overall rating, because the overall rating still remembers the spring.

Accuracy has a sibling failure on the trust side, timing drift, covered in can you trust your interval timer.

What a quiet timer looks like

• Nothing asks for anything during a session. If the app needs a permission, it asks at install or never. Bluetooth can stay off for the life of the phone and the rounds still get counted.
• No lobby between you and the timer. You installed a timer, and it should open as one. No tour first, no sign-in on the way in.
• Opening it is cheap. From install to first interval inside half a minute, and from tap to running round in a breath. That number can be measured, so it can be promised.
• Updates leave the basics alone. A release that slows the open or re-adds a nag is a regression, whatever the changelog calls it.

Where Intertakt stands

The first release ships with no required permissions. Counting down and calling phases over your music with the screen off is the whole job, and none of it needs a radio or a location fix, so none of it asks. If watch or sensor support ever arrives, it will be optional, off by default, and quiet until you go looking for it in the settings yourself.

There is no account and no launch tour. The timer is the first screen, and from install to first interval takes about thirty seconds, most of which is you picking a preset. Plans live on your device, autosaved as you edit them under names you chose, and setting them up properly is worth one minute on day one.

One commitment belongs in writing: before a release goes out, the boring checks come first, and they are “open the app from cold” and “edit a saved plan”, because those are the two things a release most loves to break. The pricing shape is laid out elsewhere: the core timer is free with no session caps, there are no ads anywhere, and Premium is a single payment.

Intertakt is out on Google Play. If you want one email when the iOS version lands, leave your address on the waitlist.