|
|
|
|
|
by yjcho9317
66 days ago
|
|
Interesting timing — I work on a mobile security SDK for Korean banking apps (200+ installs), and Accessibility abuse is basically our #1 headache. Stuff like FakeCall does exactly this — reads the UI tree, taps, types, all of it. From the system's point of view it's not that different from legit automation. Android doesn't really have a good way to tell those apart. The whole restriction thing feels a bit blunt, but I also don't know what a clean alternative would look like. Gemini gets system-level access that third-party apps can't even request, so the comparison is a bit weird. Do you run into apps that actively block Accessibility? Some banking apps just shut that down entirely. |
|