How to block apps on Android without uninstalling them

Four ways to make an app unavailable

People search “block apps on Android” and land on a mix of parental-control guides, Digital Wellbeing screenshots, and apps that ask for device-admin rights. The useful split is simpler than that list. You either still want the app installed, or you are finished with it. If you still want it installed, you are choosing how hard it is to open and how easy it is to change your mind.

Menu names move around. Google’s own Digital Wellbeing help says some steps vary by device, and Samsung often files the same tools under Digital Wellbeing and parental controls. The behavior below is the part worth planning around.

Digital Wellbeing app timers

An app timer is a daily allowance. On a phone where the Google path is intact, you open Settings, tap Digital Wellbeing, tap App timers, set a time beside the app, and confirm. When the allowance is used, the app closes and its icon dims. Timers reset at midnight. To open the app again before then, you go back and delete the timer.

That last step is the whole character of the tool. The timer is real, and the person who set it can also remove it, in the same Settings screen, the same evening. Google also offers an App limits PIN: a 4-digit code, separate from the lock screen, that stands in front of changes to those limits. Their help notes you can set a limit of zero if the goal is to keep another user out of an app. Once that PIN exists, do not hand it to the person you are trying to slow down, including the version of you that negotiates at 11 p.m.

A timer fits an app you use for a real reason and want capped per day: a game after work, a video app, a shop you fall into. It fits poorly when the decision is “I am done with this until Monday,” because Monday is a date and a timer is a budget that renews at midnight. For that shape of decision, jump to limits versus blocking.

Focus mode

Focus mode pauses a set of apps together. In Digital Wellbeing, choose the apps, then turn Focus mode on now or give it a schedule. While it is on, those apps stay paused and their notifications stay quiet. Google’s help also documents Take a break, which unpauses them for a stretch you pick.

We send people to Focus mode when the problem is a block of hours, not a single app with a reputation. Work from 9 to 5, a class, a dinner. The schedule does the remembering. Take a break is there because some of those hours have a legitimate exception, and the feature assumes you will sometimes need it. If the exception is the habit, a break button becomes the way through. That is a property of the tool, and it is fine when you want a pause you remain in charge of minute to minute.

When uninstalling is the right move

Uninstalling fits an app you have no remaining reason to open. The account can live in the cloud, the icon is gone, and the phone is lighter. It is a clean ending.

It is a clumsy block. Reinstalling is a search away, and the moment you want the app for one practical job (a code a friend sent, a login, a file) you install the whole habit again. Local data that never synced is gone with the uninstall. If the honest sentence is “I need this app on Thursday and I do not want it tonight,” leave it installed and put a duration on it.

What a launcher block changes

ReClaim replaces the home screen. That is what lets a block sit in the path of opening an app, instead of living in a second app you have to remember to consult. Long-press an app, choose Block, and pick how long. The slider steps through 5, 15, and 30 minutes, then 1, 2, 3, 6, 12, and 24 hours, then 2 days, 3 days, 1 week, 2 weeks, 1 month, 3 months, 6 months, and 1 year.

We left early unlock off on purpose. The blocked list shows the app and the time remaining, and the row expires by itself. A block only means something if the moment you want the app is the moment that cannot edit the rule. If you read that and feel a flinch, the flinch is information: you want a limit you can raise, or a reminder you can extend, and you should set that instead. Forcing a block you already plan to defeat just trains you to go around the launcher.

Block an app in ReClaim

This is the whole path, including the two Android permissions that decide whether the block survives contact with the rest of the phone.

1. Set ReClaim as the Home app. Install it and accept the Home prompt, or set it later under Android Settings, Apps, Default apps, Home app. Switching back is the same screen. Details are in the FAQ and on how it works.
2. Long-press the app and tap Block. You can do this from the home screen or from the alphabetical list.
3. Pick the duration. Short steps cover a meeting or an evening. Multi-day and multi-month steps cover “I am finished with this for a while.” The block runs until that time ends.
4. Tick the apps under Block together. Suggestions are your most-used apps from the last 7 days. That list needs Usage Access. Blocking itself works without the permission. The suggestions do not. The path is Android Settings, Apps, Special app access, Usage access, ReClaim, and it varies by phone. Our support page has the cases we see most.
5. Turn on System-wide blocking. In ReClaim: Settings, Blocking, System-wide blocking. Android then asks you to allow an Accessibility service. That service is what notices a blocked app opening from Recents, a notification, or another route, and closes it. Without it, ReClaim still refuses the open inside its own launcher and falls back to a notification everywhere else.
6. Set battery use to unrestricted. Android Settings, Apps, ReClaim, Battery. Some manufacturers also have a separate “sleeping apps” or hibernation list. If ReClaim is on it, enforcement goes quiet after the phone has been idle, which feels like the block randomly expired. It did not expire. The process was frozen. Android’s Doze and App Standby documentation is the platform behavior underneath that.

Make the block hold outside the launcher

The first version of a launcher block that only guards the launcher is a block people walk around before the day is over. A notification is an open button. Recents is an open button. Another app’s share sheet can be an open button. Android’s Accessibility service is the supported way for an app to observe those openings and close them. We ask for it in plain language, as System-wide blocking, and the launcher still runs if you skip it. You should know what you skipped: the wall then has a side door.

Usage Access is a different permission, and a smaller one. It lets ReClaim read, on the device, how long each app has been in the foreground. That powers two things on this screen: the “block together” suggestions, and any daily or weekly limit you set later. UsageStatsManager is the Android API. It is also why a limit can be slightly late if you only trust the historical total: Android is most reliable about a session once the session has ended. For a cap that has to close an app while you are still in it, the in-progress time has to be counted on top. We do that for limits. A plain block does not need it, because a block is about the clock you set, not about minutes of use.

Permissions, in one place, are on the requirements page. Nothing on that list is required to install ReClaim and use the quiet home screen. Each one turns on with the feature that needs it.

Block the app you open next

The block that fails in practice is the precise one. You block the app with the bad reputation and leave the app you open when the first one is unavailable. The second app was never the problem until it became the door. Block together exists for that pair. The suggestions are mechanical: whatever you have actually been using for the last week, not a moral list of social networks we typed in advance. If Usage Access is off, pick the companions yourself. You already know them.

A useful test before you confirm: name the app you will open in the ten seconds after this one refuses. If you can name it, it belongs on the same duration.

Schedules, for the hours that repeat

A one-off block is a decision with an end time. A schedule is that decision on a clock. In ReClaim a schedule has a name, a start, an end, the days it runs, and the apps it covers. Work hours, bedtime, a weekend morning. Schedules can overlap. If any active schedule covers an app, the app stays blocked. Turning a schedule off lifts that schedule’s block at once, which is the right escape hatch for a rule about hours, because the rule was “during this window,” and the window can be cancelled. A manual block stays put until its own timer ends.

Use a schedule when the temptation is tied to a part of the day you can describe in advance. Use a one-off block when the occasion is this afternoon, this week, this season.

What a block cannot promise

A launcher is friction you opted into. It is not a lock for another person, and it is not a medical intervention. Our disclaimer says both, and it matches how the software works: a determined person can still find a way around launcher-level enforcement, because Android is their phone. Safe mode, settings, a different home app. We would rather say that here than imply a guarantee the platform does not offer.

If the phone belongs to a child, this is the wrong guide. Look at Google Family Link, which is built for a parent account managing a child account, including app blocks and a zero-minute limit behind a PIN you hold. ReClaim is built for the person holding the phone.

If the app is something you open before you have decided to, a hard duration can be more wall than you need. Hiding it behind a short challenge is the middle setting, covered in how to stop opening apps on autopilot. And if the home screen is still a grid of invitations, start one step earlier with a minimal Android home screen, so the block is backing up a quiet first page instead of fighting a loud one.

Questions