Android

34,703 readers

2,334 active

2 users here now

DROID DOES

Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules

1. All posts must be relevant to Android devices/operating system.

2. Posts cannot be illegal or NSFW material.

3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.

4. Non-whitelisted bots will be banned.

5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.

6. Memes are not allowed to be posts, but are allowed in the comments.

7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.

8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.

Community Resources:

founded 3 years ago

moderators

Rooki@lemmy.world

L3s@lemmy.world

L4s@lemmy.world

Google is requiring mandatory developer verification for all Android apps in 2026 (thelemmy.club)

submitted 5 months ago by TheTearMiser@lemmy.world to c/android@lemmy.world

282 comments fedilink hide all child comments

If you haven't seen this yet, Google is planning to require mandatory developer identity verification for all Android apps, including apps distributed outside the Play Store, taking effect September 2026. This affects every independent and open source Android developer directly.

This is not just about the Play Store. After September 2026, on any certified Android device, applications from unverified developers will be blocked by default. The only proposed bypass, the "advanced flow", exists only as a blog post and has not appeared in any beta, dev preview, or canary release. No one outside Google has seen it.

The community has been fighting back at keepandroidopen.org:

Read the full breakdown of what this means
Sign the open letter (organisations only)
Contact your national regulators — contacts listed by country on the site
Add the countdown banner to your project

September 2026 is closer than it looks. The time to push back is now.

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

[–] Shimitar@downonthestreet.eu 3 points 5 months ago

I am sorry to say that forking AOSP is not an easy solution.

I cannot talk for Grafene as I don't know much of that organization, but I have been part of the Lineage Os organization for a little bit as a maintainer, and I can tell you that nobody is actually able to start working on such an effort as an AOSP fork.

I would gladly be happy if such a work would actually be maintained and supported long time, but I'm skeptical that anybody but a big organization has a power and a resource is to do so. After all even Linux is actually brought along by lots of organizations and also commercial organizations.

Yes, we need an open source trust platform, and I believe that is the only real way forward. I would vouch for a Linux mobile operating system, but indeed, air truly open, Android would be good as well.

permalink

fedilink

source

parent