Technology

59569 readers

3825 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

138

Google mocks Epic’s proposed reforms to end Android app market monopoly (arstechnica.com)

submitted 7 months ago by jeffw@lemmy.world to c/technology@lemmy.world

34 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ozymandias117@lemmy.world 1 points 7 months ago (1 children)

The restriction of being limited to Google Play and not other app stores implies the implementation is part of Google Play Services, and not included in AOSP

So I was curious if that’s how it’s implemented on Android - I know Google loves moving features out of AOSP

However, things like Android-Password-Store used Accessibility services through F-Droid for autotyping back when I used it

So, trying to understand what has been locked down, since I’m planning on going back to GrapheneOS

[–] FalseMyrmidon@kbin.run 4 points 7 months ago (1 children)

https://www.androidpolice.com/android-13-blocks-accessibility-services-sideloaded-apps/

It just takes an additional warning acknowledgement.

Google isn’t fully stopping sideloaded apps from using accessibility services, though. Once you’ve run into the dialog saying that accessibility services are restricted for the app in question, you can activate access under the app info screen in the top right corner via the “allow restricted settings” menu entry, so if you’re a power user interested in augmenting your phone with a legitimate app, you can still do that. This seems like a loophole that nefarious apps could circumvent by instructing users to enable restricted settings. Thus, it’s possible that Google will still change this behavior before going live with stable Android 13.

[–] ozymandias117@lemmy.world 1 points 7 months ago* (last edited 7 months ago)

Thanks!

It’s also important to note that Google is only restricting sideloaded apps. If you use an alternative app distribution platform like F-Droid or the Amazon app store, you won’t run into the accessibility services restrictions, with Google probably reasoning that applications in app stores are screened, at least to a degree.