App limits, blocking, or reminders: which one to use

The difference in one table

App limits, blocking, and reminders all reduce time in an app. They answer different questions. If you only remember one row, remember the second: what happens when you change your mind.

Android’s built-in version of the middle column is an app timer in Digital Wellbeing. It closes the app when the day’s allowance is gone, dims the icon, resets at midnight, and can be deleted in Settings unless you have set an App limits PIN. ReClaim’s limit is the same shape of idea, with a weekly cap and a choice about what “the allowance is gone” actually does. The setup for a one-off block, if that is the column you need, is in how to block apps on Android without uninstalling them.

A block is a decision with an end

A block in ReClaim is a duration on an app that is still installed. The slider runs from 5 minutes to a year. While it is active, the launcher refuses the open, and with System-wide blocking the app also gets closed if you reach it some other way. The settings list shows the time remaining. There is no control to clear it. We built it that way because the moment the block is doing its job is the moment you want it gone, and a button on that screen would be the button you press.

That makes a block a poor daily driver for an app you still need. Maps on a travel day, a messenger a client uses, the camera roll you actually have to answer from. A year-long block on any of those is a trap you will route around, and routing around is a worse habit than the original app. Save the block for a sentence you can finish: “I do not need this until Monday,” “I do not need this on the flight,” “I am done with this until the season changes.”

Schedules are blocks with a repeating clock: a name, days, a start, an end, and a set of apps. Overlapping schedules stack. If any of them covers the app, it stays blocked. Turning the schedule off lifts that schedule’s block immediately, because a schedule is a claim about hours, and hours can be called off. A manual block keeps its own end time.

A limit is a budget that repeats

A limit is for the app that earns its place and then eats the afternoon. You set a daily number of minutes. You can add a weekly number. The weekly number cannot be smaller than the daily one, because a weekly cap under the daily cap would never be the thing that matters. The screen says it plainly: a daily limit resets at midnight, and a weekly limit resets on Monday.

When the time is used, you pick one of three outcomes:

• Block for the rest of the period. The app closes, if System-wide blocking is on, and stays unavailable until the reset. Or until you raise the limit.
• Just notify me. You hear about it. The app keeps running.
• Track only. The number is recorded. Nothing interrupts you. This is for learning what a realistic cap would be before you enforce one.

There is a separate switch, off unless you turn it on: notify me at 50% and 80% of the limit. Those are warnings, not stops. They exist so the end of the allowance is not a surprise in the middle of a sentence.

Raising the limit lifts a budget block the moment you save. We check “is this over right now?” against time already used, instead of stamping a frozen lock that survives the new number. That was a deliberate fix. A cap you set too tight on Monday should not hold you hostage until Tuesday if you correct it. The tradeoff is honest: a limit can be negotiated. If you raise it every evening, you do not have a limit, you have a diary. Look at the number you keep landing on and set the cap there, or move that app to a block for the hours when the negotiation happens.

One implementation detail that changes whether the cap is real: Android’s usage history is most trustworthy once a session has ended. A limit that waited for that history would let the current session run past the cap and only notice afterward. We add the in-progress time on top of the historical total, so a “block for the rest of the period” limit can close the app while you are still in it. That close still depends on System-wide blocking. Without the Accessibility service, you get the notification path our support page describes.

A reminder is a decision at the door

A reminder does not decide the day in advance. It stops the open long enough to ask how long you intend to use the app. The first row offers 5 minutes, 1 minute, and 15 minutes. More times sit behind that row, and you can type a custom length unless you have set a max per opening. A max removes every option above it, including the custom field. There is no chip that sneaks past the ceiling.

The prompt also shows what you have already used. On a test phone, opening a music app showed 22 minutes today and a small week chart underneath, with a way back out labeled “Back to Better Things.” The point of putting today’s total on the same screen as the buttons is to make “five more minutes” land next to the time you have already spent, while you are still outside the app.

When the minutes run out, the default is a prompt: a full screen that says your time is up, with “leave” as the loud action and “add more time” as the quieter one. Adding time is allowed. The screen also counts it. If you have extended twice today, it says so. We kept the count and left off anything that resembles a streak, because a score you have to open the phone to protect is another reason to pick the phone up. The rule we use for that kind of cut is written up in our approach.

Per app, you can change what “time is up” means:

• Prompt. The reminder screen appears. Leave, or add time. This is the default.
• Close. The app closes and you land on the home screen.

Both of those depend on System-wide blocking if you want the app actually closed. With that service off, the fallback is a notification. The settings screen says this in red until you turn the service on, because a reminder that cannot close anything is easy to talk over.

If the same app keeps getting extended, its settings offer the next tool in this article: “Repeatedly reminded? A standing limit might fit better,” with a direct link to add a daily or weekly limit. The block screen points the other direction too. Under the duration it asks whether you would rather set a standing limit. The product is willing to tell you that you picked the wrong column.

A rule you can apply in a minute

Write one sentence about the app, in the form you would say out loud.

• “I do not want this available until Friday.” Block. Include the app you open when this one is missing. Steps are in the blocking guide.
• “I want this during the workday and nowhere near bed.” Schedule, which is a repeating block, for the hours. A limit if the workday itself runs long.
• “I use this for real tasks and I lose an hour in it.” Daily limit, action set to block for the rest of the period, with the 50% and 80% warnings on until the number feels fair. Start from a week of “track only” if you do not know the number yet.
• “I open this before I have thought about it.” Reminder, and probably a hide as well. The habit version of this problem is its own guide: stop opening apps on autopilot.

If your sentence contains both “I need it today” and “I must not be able to change this,” the sentence is two tools fighting. Split them by time of day. A schedule can hard-block the evening while a limit governs the afternoon.

How to combine them without noise

A clean stack looks like this. The home screen only holds apps you mean to open, which is the job of a minimal Android home screen. Two or three apps you have genuinely quit for a stretch get a block or a schedule. One or two apps you use and overuse get a limit with “block for the rest of the period.” One ambiguous app, often video or a browser, gets a reminder with a max per opening so the custom field cannot become “four hours.”

A noisy stack puts a reminder on an app that is already hard-blocked. The reminder never runs, because the app never opens, and you have an extra setting to forget. It also puts a four-hour daily limit on an app and calls it restraint. Four hours will almost always be reached by accident of a long session, and the limit will feel like a bug. Set the number at the edge of a session you would still endorse tomorrow morning.

You can put a limit and a reminder on the same app. The reminder governs the opening. The limit governs the sum. That pair is what the in-app link is pointing at when extensions pile up. A manual block replaces both until it expires. Let it.

Numbers that are too soft to count

We would rather you set a slightly generous limit you keep than a harsh one you raise every night. The raising is visible, on purpose. The reminder’s “Extended 2× today” is the same idea at the scale of a single open. What we will not add is a badge for surviving the day, because checking the badge is another open.

A weekly cap is the right second number when the daily number is honest and the week still gets away from you: a social app at 20 minutes a day is two hours and twenty minutes if you hit it every day, and you might want the week to stop earlier than that. Set the weekly field. It cannot undercut the daily field, and it resets Monday, so a Sunday night binge and a Monday morning reset are different events. Plan for that if Sunday is your weak day. A manual block over the weekend will hold where a weekly budget still has remainder.

What has to be turned on

Limits need Usage Access. They are a measurement, and Android keeps that measurement behind a special permission. Blocking and hiding work without it. Suggestions for “block together,” and the 7-day picture behind them, need it too.

Anything that closes an app from outside the launcher needs System-wide blocking, which is ReClaim’s Accessibility service. Reminders set to Close need it. Limits set to block for the rest of the period need it. Manual blocks need it if the app can be opened from a notification or Recents. With the service off, you still get the launcher’s own refusal and a notification. The phone will also need ReClaim set to unrestricted battery use, or a manufacturer power saver can pause the service after the screen sleeps and the rules appear to vanish. Both fixes are on the support page, and the full permission list is on requirements.

None of this is a clinical program. If the pattern you are trying to change is past a tool on a home screen, the disclaimer points at a professional, and that is the right handoff.

Questions