Accessibility Service vs Banking Apps: How do you handle false flags?
Hi everyone,
I am building a digital wellbeing app that blocks only the Shorts/Reels pages inside YouTube and Instagram, leaving the rest of the app open. Because I need to check what is on the screen, I have to use an AccessibilityService with canRetrieveWindowContent="true".
How I optimized it for safety:
Targeted Packages: It only runs inside a few social media apps. It is completely inactive everywhere else.
No View IDs: I don't use View IDs or read messages. It only looks at the basic layout depth.
100% Offline: No data is collected or sent to any server.
The Problem:
Even though the code is safe, banking apps flag my app as a threat simply because a third-party accessibility service is running on the phone.
My Questions:
Workarounds: How do other devs deal with this? Is making a Quick Settings Tile to let users "Pause" the app before opening a bank app the best workaround?
Other APIs: Is there another approach? UsageStatsManager only tracks the whole app package, so I would have to block all of YouTube, which breaks my main feature.
Thanks for any help!