Yeah, we should just ironically lean into it even harder and call it “backdooring”.

Jokes aside, when has pandering to people to change the status quo of colloquial word use ever worked?

It's called "sideloading" because you're sneakily installing software without the manufacturer's consent. Remember it's never your device, you just have permission to use it.

I think "sideloading" is a completely ok term. it says what it is,, you load an app, not with the intended method (appstores) but from an alternative source, aside the official store. not a native English speaker, so I might not fully understand the possible connotations with this particular word, but I do not personally see anything wrong with it.

Offline installation.

Still waiting to see chatcontrol happen. Maybe I’m naive, but I don’t believe it will happen.

if we're talking about the EU, for a provider the size of Google, not allowing third party application installs is illegal in the EU under the Digital Markets Act

Only works if everyone stops helping Google to turn the Web into ChromeOS Platform.

A government probably wouldn't have to push very hard for Google to revoke a dev's signing key, blocking apps signed with that key. So I don't see a difference. Technically sideloading will be possible, but Google will still have control of what apps can run on devices.

>Verified developers will have the same freedom to distribute their apps directly to users through sideloading or through any app store they prefer.

So it’s the same then. Google can just “unverify” a developer who has published an app the kings don’t approve of.

Unverified developers can still use adb to install whatever they choose per the link:

“How does developer verification impact my use of Android Studio?

We are working to ensure these changes don’t have an impact on your day-to-day workflow so you can continue building your apps as smoothly as possible. Participating in developer verification will not affect your experience in Android Studio, the official IDE for Android app development. You will continue to be able to build and run an app even if your identity is not verified. Android Studio is unaffected because deployments performed with adb, which Android Studio uses behind the scenes to push builds to devices, is unaffected. You can continue to develop, debug, and test your app locally by deploying to both emulators and physical devices, just as you do now.”

For clarity, they're requiring apps to be signed by a verified developer on certified Android devices. You can still side load, but the verification is still required for the side loaded apps.

> Sideloading is still possible if the developer key is registered

To all intents and purposes it is not allowed, then. Google becomes the gate keeper by controlling registration

"Trust us"