App Blocking

The list is drawn from the phone itself rather than from a catalogue, so it shows what is really there, including the things that arrived last week without being mentioned. Each row carries the app name, its icon, how long it has been used in the last seven days, and its current state. New arrivals are marked, which is usually where a parent’s attention should go first.

The three states are deliberately few. Allowed means nothing happens. Paused means the app stops during hours you choose and works normally the rest of the time. Blocked means it does not open at all until you change your mind. There is no partial mode, no warning-only mode, and no per-feature tinkering inside somebody else’s app, because those things do not work reliably and pretending otherwise just makes the tool untrustworthy.

States are per child and change immediately. Set a rule from your phone while standing in a supermarket and it applies within seconds. A pending request from your child appears at the top of the same page, so approving an exception is one tap in the place you were already looking.

Blocking outright is the right answer for a small number of things: an app well outside your child’s age range, a VPN or proxy app installed to route around filtering, a gambling or dating app that has no business on the phone at all, or something that arrived from outside the store and you cannot identify. These are decisions rather than negotiations, and blocking makes them clean.

Pausing is the right answer for almost everything else. The problem with a game is rarely that it exists, it is that it exists at eleven at night and during homework. A pause covers exactly those hours and leaves the rest of the day alone, which means the rule is about time rather than about the app being bad. Children argue far less with a rule that has an end time attached.

The failure mode of over-blocking is worth naming, because it is common. Block six apps at once and you have not removed six problems, you have created one adversary. Effort that would have gone into using the phone goes into finding another way onto the same platform through a browser, a friend’s device, or a lookalike app with a different name. A short, defensible list of blocks holds. A long one leaks.

A reasonable starting position is one block and one pause. Block the single app you genuinely do not want on the device. Pause the two apps at the top of the time list during school hours and after bedtime. Then leave it a fortnight before touching anything else.

Tap a blocked app and it opens onto a full screen message. It gives the app name, the rule that applies, whether the block is permanent or on a schedule, when it will next be available if there is a schedule, and the name of the parent who set it. Below that is a button to send a request, and nothing else. No shame, no countdown timer designed to nag, no cartoon padlock.

Some products in this category disguise a block as a crash or an error, on the theory that a child who thinks the app is broken will stop trying. It is a bad idea for three reasons. It teaches a child that their phone is unreliable, which sends them to a repair shop or a factory reset. It wastes everyone’s time on troubleshooting a problem that does not exist. And when the truth surfaces, as it always does, the thing that gets damaged is not the app rule but your credibility.

A named block is honest and, unexpectedly, more effective. There is nothing to investigate and nothing to discover. The rule is visible, it has an author, and the only route around it is to ask. That converts a technical contest into a conversation, which is the contest you can win.

The child app also carries the full list of current rules, so nothing is a surprise at the moment of use. A child can look at their own phone on Sunday evening and see exactly which apps pause at nine, without having to trigger each one to find out.

From the block screen, your child can ask. The request carries the app, the current rule, the time it was sent, and up to a sentence of their own explanation. It arrives on your panel where you can grant fifteen minutes, an hour, the rest of the evening, or a permanent change, or simply decline it. Granting a temporary exception does not alter the underlying rule, which quietly returns afterwards without a second conversation.

Parents sometimes assume this will produce a flood. In practice it does the opposite. When asking is easy and the answer arrives quickly, requests are few and specific: a group project in a chat app during homework hours, a video call with a grandparent after bedtime, a game on a Friday when the schedule assumes a school night. Those are all reasonable, and each one is a small deposit of goodwill.

Requests that are refused are worth answering rather than ignoring. A declined request with no reply reads as a wall, and a wall is what makes a teenager start looking for gaps. A one-line answer costs nothing and keeps the system running on agreement rather than on enforcement.

Repeated requests for the same app are information, not nuisance. Three requests in a week for the same chat app during homework usually means the homework genuinely involves that chat app, and the right fix is to change the rule rather than to keep declining the symptom.

You can act on a whole category, which is the efficient way to handle games or social apps as a group, and it has the useful property of covering the game that gets installed next week without you doing anything. Category rules are a good match for schedules: pause all games during school hours, pause social apps after bedtime, and stop maintaining a list by hand.

Single app rules are for the specific case, and they always win over the category. Pause every game after nine but allow one that a child plays with a cousin abroad. Block one social app while leaving the rest alone. The panel shows which rule is winning on each row, so an app that is blocked by a category and allowed individually is not a mystery.

Then there is the floor. The phone dialler, emergency calling, messages, the clock and alarm, the settings needed for accessibility, and the family app itself cannot be blocked by any rule you set. This is not a limitation we regret. A phone that cannot ring for help is a worse outcome than any app you were trying to stop, and no schedule, budget, or bedtime rule is allowed to take priority over that.

Blocking is also not uninstalling. The app stays on the phone with its data intact, and unblocking restores it exactly as it was. Nothing is deleted, and there is no punishment mechanic that removes a child’s saved progress in a game.