795
Google Confirms Non-ADB APK Installs Will Require Developer Registration (hackaday.com)
submitted 1 year ago by to c/technology@lemmy.world
257 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 55 points 1 year ago (6 children)

So now 3rd party app stores need an ADB loopback to work around that.

Not hard to do, but uselessly annoying.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 5 points 1 year ago (2 children)

    That's only if the apps distributed are unverified. Mind, the EU already requires app stores to document the identities of devs, but there are loopholes for Small enterprises. In 2027, manufacturers need to document the identities of their suppliers. There are still exceptions for non-profit open source projects, but that's not what Google is. Surely, no one here wants Google to avoid regulations by investing in open source.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 year ago (1 child)

    I believe F-Droid signs the packages it distributes so that creates a painful choke point. Revoke F-Droid's key and it will break all of F-Droid instantaneously. The only exception for F-Droid's signing is if the build is reproducible, which is a high bar for a lot of projects, and then F-Droid will use the upstream signature.

    Also, they're trying to close the ADB loophole.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    I expect phones in the EU are going to become a lot more locked down in the next 14 months, like Samsung is already showing. But also think that Google will try its best to make developing for Android easy to get into.

  • permalink
  • fedilink
  • source
  • parent