🚨 Say that I were to give a talk to EU policy makers and OSS communities at a very big conference tomorrow..

and that I want to spend half of my talk on how Google is locking down #Android through:
1. Device attestation
2. Developer registration
3. Age/identity verification

What should I absolutely include? 👀

Input is welcome, sorry for the short notice. Plain language + realistic calls to action pls.

@fdroidorg @GrapheneOS @postmarketOS @Fairphone @appfair @fsfe @murena @volla @IzzyOnDroid

Boosting and tagging is appreciated, DM's are welcome too.

I really want to get this right, so please only use verified information. And yes, I'll be mentioning https://keepandroidopen.org/ extensively.

(And yes I will also mention Apple and the role of the DMA, but only briefly. More info: https://mastodon.social/@kirschner/116440678455335985)

Keep Android Open

Your phone is about to stop being yours. In September 2026, Google will block every Android app whose developer hasn't registered with them.

I'll start with the #opensource strategy and EU tech sovereignty package, and good things happening and alternatives being build etc.

Then mention how the mobile ecosystem is one of the last frontiers left critically assessed.

I'll share how Google is closing down Android (input welcome!). 

And that we need to promote, fund, regulate and perhaps even build open (EU) alternatives in the mobile ecosystem if we don't want to increasingly become captured by 2 US big tech companies.

About age/identity verification through the new EU ID wallets, I'll mention something about the necessity of offering this through open apps / app stores. Google is all too eager to become a middleman for these services:

https://reclaimthenet.org/google-wants-to-be-the-id-checkpoint-for-europes-internet

@Gina honestly, for what concerns _required_ government interaction - like identity paperwork, taxes, or health, these functions should absolutely be priority for NOT working through Chrome or Google -

For example, I often have to use Chrome browser instead of Firefox or Librewolf, bc the government sites simply don't function unless it's Chrome.

Next priority = banks. I should not be required to have a phone at all to do banking, but if I do, I should be able to use GrapheneOS or other.

@Joy_intl
@Gina

it might be kinda useful to policy types - and I don't think I've ever seen such a thing - to have a sort of catalog of what are established uses of mobile devices and which of those need to be ring-fenced, protected from the surveillance cartel

The list is quite long... from calls/messaging, to identity, location, camera/audio, health, payments, banking, any other sensitive commercial/personal interactions etc.

The techbros know exactly what they are after, but we dont