What Apple's Screen Time API can and cannot do

When you pick apps, iOS returns opaque tokens. Not names, not bundle identifiers, not icons. A token is a sealed handle: the app can tell iOS to block it, and can ask iOS to draw it on screen, and can never read it.

This is why a well built blocker shows you a count and lets iOS render the list itself. It also means those tokens cannot be sent to a server, because they mean nothing outside your device.

The upshot for you is good: the company behind the app genuinely does not know you blocked a dating app. Not as a policy. As a property of the system.

Screen Time usage is rendered by iOS inside a view the app cannot inspect. An app can be told that a threshold was crossed, and nothing else.

So when a blocker tells you it saved you four hours this week, it either has that number from somewhere it should not, or it made it up. Almost always the second. There is no API that returns it.

Warden never shows an hours-saved figure for this reason. It shows the length of your streak and how many times you asked, both of which it actually knows.

The screen you see when you open a blocked app allows one icon, a title, a subtitle and two button labels. That is the entire surface.

A button on it cannot open an app. It can close the blocked app, or dismiss itself. That is the whole menu. So when a blocker asks you to tap through a notification to get to its own screen, that is not laziness, it is the only route Apple provides.

The parts that watch your schedule run as background extensions with a very small budget. Enough to read local state, set a shield, fire one network call, and return.

This is why serious blockers keep their logic on the device and their state small. Anything that needs a round trip to decide whether to block you is a blocker that fails open when the network is slow.

Each of these limits exists because the alternative is worse. An app that could read your app list could sell it. An app that could permanently lock your phone could be used against you by someone who installed it on your behalf.

The honest position for anyone building here is to say where the ceiling is and design under it, rather than implying the ceiling is not there. Ask any blocker you are considering what happens when its permission is revoked in Settings. If the answer is that nothing happens and nobody is told, you know how much thought went into it.