Google To Kill a Bunch of Useful Android Apps That Rely On Accessibility Services (androidpolice.com)

Slashdot reader Lauren Weinstein writes from a blog: My inbox has been filling today with questions regarding Google's new warning to Android application developers that they will no longer be able to access Android accessibility service functions in their apps, unless they can demonstrate that those functions are specifically being used to help users with "disabilities" (a term not defined by Google in the warning). Beyond the overall vagueness when it comes to what is meant by disabilities, this entire approach by Google seems utterly wrongheaded and misguided. "While the intended purpose is for developers to create apps for users with disabilities, the API is often used for other functionality (to overlay content, fill in text fields, etc.)," reports Android Police. "LastPass, Universal Copy, Clipboard Actions, Cerberus, Signal Spy, Tasker, and Network Monitor Mini are just a few examples of applications heavily using this API." It's likely Google is cracking down on apps that use Accessibility Services due to the security risks they pose. "Once granted the right permissions, the API can be used to read data from other apps," reports Android Police.
The developer of BatterySaver received the following message from Google:

We're contacting you because your app, BatterySaver System Shortcut, with package name com.floriandraschbacher.batterysaver.free is requesting the 'android.permission.BIND_ACCESSIBILITY_SERVICE.' Apps requesting accessibility services should only be used to help users with disabilities use Android devices and apps. Your app must comply with our Permissions policy and the Prominent Disclosure requirements of our User Data policy.

Action required: If you aren't already doing so, you must explain to users how your app is using the 'android.permission.BIND_ACCESSIBILITY_SERVICE' to help users with disabilities use Android devices and apps. Apps that fail to meet this requirement within 30 days may be removed from Google Play. Alternatively, you can remove any requests for accessibility services within your app. You can also choose to unpublish your app.

Alternatively, you can choose to unpublish the app. All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts.

If you've reviewed the policy and feel we may have been in error, please reach out to our policy support team. One of my colleagues will get back to you within 2 business days.

Regards,

The Google Play Review Team

Comments

some of these are useful because android sucks

[Anonymous Coward]

some of these cover gaps in android and make it suck less

when my devices are sluggish and quirky greenify is great

how about google fixes android suck before breaking viable work-arounds?

What they're really doing...

[fieldstone]

Is cracking down on apps that use accessibility services as a way of getting around not having root access. Google really isn't very friendly to users having control over their own device. So much for "Don't be evil".

Re:What they're really doing...

[Anonymous Coward]

No, what they're really doing is making Android more secure.

After your emotions settle and your knee-jerk rant that seems equivalent to "Bwaaaaa they're taking away my favorite app! QQ", you might eventually realize that removing gaping security holes is a good thing.

Re:What they're really doing...

[Dutch Gun]

I don't WANT a random app to be able to skirt around not having root access by claiming to need permissions for "Accessibiliy". Google is doing the right thing here, even if the approach may be a bit clumsy or ham-fisted. They were rightly panned a while back (right here on Slashdot) when shown how the Accessibility API could lead to security issues and they dismissed it as "not a bug / working as intended".

Android developers were using an API for purposes it was clearly never intended for. Only now it's understood that those APIs have security implications, so those "clever" hacks may no longer be viable. Google is now working to close those loopholes a bit by making sure app developers justify the use of those APIs, and the response is "Google Evil!" Perfect proof that you can twist *anything* to make it sound nefarious.

So I don't get to write the program that I want

[innocent_white_lamb]

So I don't get to write the program that I want even though the functionality is there.

Remind me again why it's worth learning to write programs. I always thought it was so I could create the functionality that I wanted to create; something is missing here that I want or can use so I'll make a program to fill in that gap.

Can't do that any more unless you have permission from the higher-ups, I guess. So much for my computer, my rules.

Re:It's unfortunate truth about accessibility feat

[AvitarX]

Google seems to be saying "tell us how your app helps access" not sucks to be you.

They're making a small hurdle to have apps distributed in the official store, they don't seem to be eliminating the API or blocking apps that actually are for access.