An Android app blocker that doesn't require accessibility access
An Android app blocker that restricts distracting apps without using the Accessibility Service, avoiding conflicts with banking and other security-sensitive apps.
Android app blockers that don't require accessibility access?
Android developers in a certain country are incredibly stupid and don't allow me to use my app blocker and their app at the same time for "security reasons" because the app blocker uses accessibility. such bs lol Hence the question. I don't mind paying a one-time fee if I have to.
The problem, in the searcher’s words
My app blocker won't work at the same time as my banking app because the bank blocks accessibility services for 'security reasons.' So I either have to turn off my app blocker every time I need to use the bank app, or give up blocking apps entirely.
Is there an Android app blocker that doesn't use the Accessibility API, so it won't get flagged or blocked by security-sensitive apps? I'd pay for a one-time purchase if something like this actually exists instead of relying on the usual accessibility-based blockers.
What the thread shows
The OP identifies a real technical conflict (accessibility-based blockers vs. security apps) and states willingness to pay, but only one other user responds, and their suggestion is an existing built-in Android feature rather than corroboration of the problem.
“Android developers in a certain country are incredibly stupid and don't allow me to use my app blocker and their app at the same time for "security reasons" because the app blocker uses accessibility. such bs lol”
“I don't mind paying a one-time fee if I have to.”
“hi, so i currently use modes and routines, its a built in app and you can create a mode that turns on at a certain time (or you can turn it on whenever) and you can limit access to only a few apps.”
Target customer
Who
Android users who rely on app blockers for focus/productivity but also need to use banking or other security-sensitive apps that refuse to run alongside accessibility services.
Context
This surfaces when a bank or government app detects an active accessibility service and blocks itself for 'security reasons,' forcing the user to disable their blocker just to complete a task.
What to build
- App blocking via a non-Accessibility mechanism (e.g. UsageStatsManager or Device Admin APIs) instead of Accessibility Service
- Simple blacklist/whitelist of apps to restrict
- Scheduled or manual-toggle block sessions
- One-time purchase pricing (no subscription)
- Clear messaging/testing confirming compatibility with common banking apps
Build note — Most Android app blockers rely on the Accessibility Service to detect foreground apps, which is exactly what triggers bank-app security checks. Alternatives worth evaluating include UsageStatsManager (usage-access permission), Digital Wellbeing's native App Timer APIs, and Device Policy Manager for MDM-style blocking — each has different reliability and permission tradeoffs that would need real device testing against specific banking apps.
Later, if it lands
Who’s already out there
Built-in Android feature (mentioned by a commenter) that lets users create scheduled modes limiting access to a set of apps.
Gap: It's a native, low-customization tool bundled with the OS — not a dedicated blocker product, and feature depth/availability varies by manufacturer and Android version.
Third-party Android app that blocks selected apps and websites using the Accessibility Service.
Gap: Uses the same Accessibility Service mechanism that causes the exact conflict the OP describes with security-sensitive apps.
Demand read
The OP explicitly signals willingness to pay for a fix, and the underlying conflict (accessibility-based blockers vs. security app restrictions) is a structural platform issue that could recur for other users in regions with strict banking security policies — but this is inferred from a single voice, not confirmed by others in the thread.
Worth digging into before you build
4 to considerNo idea is a sure thing at this stage — these are open questions worth checking yourself, not a verdict against building it.
Thin Source
Only 2 comments and a short post body; limited material to validate broader demand.
Single Voice
Only the OP describes the accessibility/security-app conflict; the sole commenter offers a workaround rather than corroborating the pain.
Already Solved
Commenter points to Android's built-in 'Modes and Routines' feature as already addressing the need to limit apps without accessibility conflicts.
Verify Competitors
Uncertain of exact feature set/current status of 'Modes and Routines' and AppBlock; confidence marked medium, should be reviewed.