I pity people who won't be able to sideload because of Google copying
Apple's anti-consumer Draconian control over your personal device.
To that end, I'd like to put, in one place, the answer to this question:
Q: What is Google doing to hinder sideloading by normal people?
A: ?
:: when apps have included a new Google SDK which insists that the app was
:: installed by the Google Play Store and by no other mechanisms out there.
Arno Welzel wrote:
To that end, I'd like to put, in one place, the answer to this question: >>> Q: What is Google doing to hinder sideloading by normal people?
A: ?
Nothing. You can still sideload what you want.
Hi Arno,
I have grandchildren who say stuff like that which they "think" is correct, but that's because they have no idea what they have not been exposed to.
I get it you have no idea what Google is doing, now, today, to add friction to sideloading, but there are those of us who run into that friction daily.
Basically, most of us are aware Google is adding many (many!) different points of friction such that only the most technical people will sideload.
However in the near future apps which are not registered at Google Play
by a registered developer account, will not be installed any longer - no
matter where they come from.
The fact that Google is adding more than a dozen distinct points of
friction to the sideloading process means you have to discuss all of them.
<https://newpipe.net>
What's YOUR workaround fix to the permanent loss of those apps, Arno?
:: when apps have included a new Google SDK which insists that the app was
:: installed by the Google Play Store and by no other mechanisms out there.
What "new Google SDK" do you refer to?
Geezus Arno. Seriously. Every person using Aurora Store knows about this. Everyone using adb to install apps, knows about this.
As does everyone using Muntashirakon App Manager to install their APKs.
Why don't YOU know about this?
Arno Welzel wrote:
The fact that Google is adding more than a dozen distinct points ofNo - not "adding". There are just doing it in the future.
friction to the sideloading process means you have to discuss all of them. >>
Hi Arno,
I'm glad you are here 'cuz you're an actual developer, who sees things different than I see them, as a mere user, so we can team up together.
a. I know some stuff you don't know ('cuz I ran into it empirically)
b. You know a LOT of stuff I will never know ('cuz you're a developer)
We can work together so that the entire team is edified on this topic.
Just a minor correction. Some of the dozen things are happening NOW.
For example, I've run into the need for spoofing, which is simply
additional sideloading friction added by Google (through a sneaky route).
Also, people have reported on the Telegram channel that they're already run into the 24-hour waiting period, so it seems (AFAIK) it's being "rolled
out".
Having ADB and split APKs was never desgined to "add friction to sideloading"
but is a complete different way of loading apps to avoid data volume by omitting
parts a user don't need anyway - for example all regional or language
specific elements if you don't use certain regions or languages on your
device.
I am sure you meant "AAB and split APKs" where I'm very familiar with the logically-sounding excuses Apple gives for adding friction to sideloading.
Apple's MARKETING playbook is to restrict control in the guise of security. IMHO, Google is simply copying from Apple's playbook...but for bit size.
let's be clear, means NOBODY ELSE felt any need for the "value" it brings.
My point?
There is no value. (practically speaking).
It's a way to limit people from sideloading APKs by adding more friction.
If it was such a great format, everyone would use it.
And yet, the fact is almost nobody uses it (as far as I am aware).
Worse, let's not forget Google forgot to add a native split apk installer . Now that's odd.
Why would a company that foists split apk's upon us, accidentally "forget"
to add a split-APK installer to the Android operating system. Funny huh?
The point is it's clear to me Google did it for one reason only.
To add friction to sideloading.
Google's friction being added to sideloading makes some apps impossible.
Library name? Is it part of AndroidX?
Actually, since you've written professional apps, you know better'n I do.
But it is not AndroidX, as there's a Google Maven dependency.
The API has the super secret hard-to-guess super hidden secret name of
*Google Play Integrity API*
<com.google.android.play.core.integrity>
IntegrityManager, StandardIntegrityManager, IntegrityTokenRequest,
<https://developer.android.com/google/play/integrity/overview>
<https://developer.android.com/google/play/integrity/reference/com/google/android/play/core/integrity/package-summary>
<https://developer.android.com/google/play/integrity/remediation>
But the Play Integrity Android library is what developers add to their app. Google documents SDK providers integrating it into their own SDKs.
That friction will be felt by anyone who tries to sideload, do you agree?
For example, a Gradle Android project can declare a dependency like:
repositories {
google()
mavenCentral()
}
dependencies {
implementation("com.google.android.play:integrity:<version>")
}
First off, I never disagree with a logically sensible statement, so rest assured that I'm aware that, oh, say, NewPipe could deliver their product through the Google Play Store as a split APK and NewPipe could also go to
the expense of setting up their own distribution mechanism, but nobody is talking about that when we talk about Google adding sideloading friction.
We're always talking about apps on the Google Play Repository, Arno.
Since you're a developer, I'll ask it this way to get you to think:
QUESTION: I want to create an app, and have it distributed on the
Google Play Repository, how are you suggesting I ask Google
to distribute it as a single APK and not as a split APK please.
I'm not confused, Arno. Not at all. You're the one who said all the sideloading friction was in the future, and I simply pointed out it's now.
Note that "someone" (Google?) created the APK format, for example, and someone put an APK installer native on Android and everyone adopted that
APK format, so if the format is actually useful, everyone will adopt it.
Nobody adopted the split-APK format.
Again, I'm logical, Arno. I don't think anyone would disagree that AAB/split-APK distribution makes independent backup, transfer and
restoration of applications more cumbersome for regular users, and
therefore has the practical effect of adding friction to sideloading .
Android comes with a package installer, which is part of the operating system, and which handles regular APKs, so why not update it to splits?
Arno Welzel wrote:
First off, I never disagree with a logically sensible statement, so rest >>> assured that I'm aware that, oh, say, NewPipe could deliver their product >>> through the Google Play Store as a split APK and NewPipe could also go to >>> the expense of setting up their own distribution mechanism, but nobody is >>> talking about that when we talk about Google adding sideloading friction. >>NewPipe is not available on Google Play at all.
Hi Arno,
It's good we're so DIFFERENT cuz you have developer knowledge while I have expert-user empirical experience so working together we can help others.
While NewPipe was never on the Google Play Store, the problem is that
google is forcing these apps off the market that are NOT on Google Play.
This is a HUGE threat to sideloading that you don't seem to be aware of.
In theory they could try to distribute it as single APK through Google
Play. But since Google may not accept this app anyway, they don't even
try it. RVX is also not available on Google Play for the same reasons,
since it violates their policy. But you can still download RVX as APK on
a website and install it - because sideloading is still possible.
Sideloading will NOT be possible for NewPipe. Read their documentation. NewPipe dies the very day that Google turns on the developer verification.
Build and upload an APK file to the developer console and not an AAB file.
We cannot tell Google Play, for a normal new public app, to serve everyone this one universal APK instead of split/device-optimized APKs although APK publishing remains supported for apps that were created before August 2021.
Being a developer, you should know that.
<https://support.google.com/googleplay/android-developer/answer/9844279>
does not mean Android makes it hard to do sideloading in general.
I seriously don't understand that sentence. I can create copies of apps published on Google Play in seconds, so I'm not sure what that even means.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498678:20:35 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 912 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,867 |