Timed Rewards vs. App Blockers: Check What Your Tool Really Does
By Erik Nilsen · Kroni6 min read
Short answer: Not necessarily. In a family app, a timed reward often just counts down the time you agreed on. The game on the tablet or console keeps running until someone stops it. That could be an adult, your child, or a setting in the device's own system. Whether anything stops on its own depends on the device, the game and which controls you have actually turned on.
So check before you rely on it. This guide helps you write down what you expect, tell a countdown apart from a real block, and test it on the device your child actually uses.
Three timers that look alike but do different things
Parents often mix up three kinds of timers:
- Reward countdown: Shows how much of the agreed time is left, for example 30 minutes of game time your child has earned. It keeps track of the agreement. It has no control over other apps.
- Operating system controls: Settings built in by the maker of the phone, tablet or console. Some of them can limit apps or the whole device. What they do varies between makers and versions.
- Task countdown: A timer that helps your child stay focused on a chore, like tidying their room in 15 minutes. It has nothing to do with screen time.
In Kroni, a timed reward can track the time your family has agreed on. The focus mode countdown shows how long a task is expected to take. Neither one blocks other apps, sets usage limits or connects to the device's parental controls. When the reward time runs out, the agreement is what counts, and an adult follows up.
That isn't necessarily a weakness. Many families just want one clear, shared clock. But if you need the game to actually close, you have to find that in another tool and test it.
Step 1: Write down what you actually expect
Be specific before you compare anything. "Less screen time" is not something you can test. "Minecraft on the tablet should not open after 30 minutes" is.
Answer these questions for each device:
- Which device? Phone, tablet, computer or console, and who owns it?
- Which apps or games does the agreement cover?
- What should happen when time is up? A notification, the app closing, the whole device locking, or your child putting it away?
- What starts the time? Your child tapping something, an adult doing it, or the app being opened?
- Who follows up if nothing stops on its own?
This is often where parents notice they expect different things from different devices. A reminder may be enough for the computer in the living room, while the tablet in the bedroom needs more.
Step 2: Check the documentation, and date it
Once you know what you need, read what the tool says it does. A few simple rules:
- Use the maker's own help pages, not forums or old blog posts. Settings change between versions.
- Write down the date you read the page and the system version on the device. Then you know what to recheck after an update.
- Look for specific verbs. "Tracks," "shows" and "reminds" mean something different from "blocks," "locks" or "prevents."
- Check the exceptions. Does it mention apps that are always allowed, whether your child can ask for more time, or whether a separate child account is needed?
If it doesn't clearly say a feature stops an app, assume it doesn't until you have tested it.
Step 3: Test on the real device
Documentation is one thing. Real life is another. Run a short test before you promise your child anything or build an agreement on it.
- Set a short time, such as 5 minutes, so you don't have to wait long.
- Start the game the way your child usually does.
- Let the time run out without touching anything.
- Write down exactly what happens. Is there a notification? Does the game close? Can it be reopened? What happens if the device is offline?
- Try it once more with your child there, so you both see the same thing.
What you write down is the answer for that specific device. It doesn't automatically apply to a sibling's phone or the console.
Example: the Carter family (fictional)
The Carter family is made up and only shows how to fill in the sheet. Maya (10) has earned 30 minutes of game time by doing homework and setting the table.
| Field | Reward countdown in the family app | Controls in the tablet's system |
|---|---|---|
| Device and app | The family's shared tablet, Maya's favorite game | Same tablet, same game |
| Desired result | Maya and her parents see the same time left | The game can't be used after the agreed time |
| What starts the time | Maya starts the reward on the shared device | Per the maker's documentation, read and dated by the parents |
| What happens when time runs out | The countdown ends, the game keeps running | Recorded only after the parents' own test |
| Who follows up | Mom speaks up and Maya puts the tablet away | An adult checks the setting is still on after updates |
| Observed on the device | The game kept running until Maya closed it herself | Filled in once the test is done |
The example doesn't tell you what your tablet does. It shows that the two columns need to be checked separately, and that the "observed" row only holds what you have seen yourself.
Copyable worksheet: capability check per device
Copy the table and make one for each device. Fill in the blank fields yourself.
| Field | Reward countdown | Controls in the device's system |
|---|---|---|
| Device (type, owner, system version) | ||
| App or game the agreement covers | ||
| Desired result | ||
| What starts the time | ||
| What happens when time runs out, per the documentation | ||
| Source and date read | ||
| Who follows up | ||
| Test date | ||
| Observed on the device | ||
| Recheck after update (yes/no) |
Getting started this week
- Monday: Do Step 1 for every screen in the house. Ten minutes is enough.
- Tuesday: Read the maker's help pages for the device that matters most, and note the date.
- Wednesday: Run the 5-minute test and write down what happened.
- Thursday: Talk with your child about what happens when time is up, and who says so.
- Sunday: Look over the sheet. Did your expectations match what you saw?
How much time can be earned, and how, is a separate topic. Read more in Screen Time and Rewards: Make an Agreement That Works.
When a countdown is enough, and when it isn't
A shared countdown works well when your child mostly keeps agreements and you mainly need a clear clock everyone can see. Then Kroni does its job: your child does chores, uses the agreed reward, and the countdown shows how much of the agreed time is left.
If you need an app to actually close, look into the device's own controls. You can also use both. The countdown works as the agreement and the motivation, and the system control is a fence where one is needed. What matters is that you know which tool does what, because you tested it yourself.
Frequently asked questions
- Does a timed reward stop the game automatically when time is up?
- Not necessarily. A reward countdown shows how much of the agreed time is left, but the game keeps running until someone stops it. Whether anything closes on its own depends on the device's own controls, so test it on that device.
- What's the difference between a reward countdown and parental controls on a phone?
- The countdown keeps track of your family's agreement and shows the time left. Parental controls in the operating system are settings from the maker that can limit apps or the device. Read the maker's own help pages, note the date and test it yourself.
- Do I need to test again after a system update?
- It's a good idea. Settings and features can change between versions. Note the system version and test date on the worksheet, and run a quick 5-minute test again after major updates.
