• Re: What, exactly, is Google doing, to copy Apple's anti-consumer sidel

    From Arno Welzel@3:633/10 to All on Thursday, October 01, 2026 09:24:54
    Subject: Re: What, exactly, is Google doing, to copy Apple's anti-consumer sideloading policy?

    Maria Sophia, 2026-09-28 19:55:

    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: ?

    Nothing. You can still sideload what you want.

    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.

    But even this can be circumvented, even though it is quite cumbersome:

    <https://keepandroidopen.org/>

    [...]> :: This script will fix one of Google's attempts at stopping sideloading
    :: 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?


    --
    Arno Welzel
    https://arnowelzel.de

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Arno Welzel@3:633/10 to All on Thursday, October 01, 2026 14:20:22
    Subject: Re: What, exactly, is Google doing, to copy Apple's anti-consumer sideloading policy?

    Maria Sophia, 2026-10-01 10:24:

    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.

    I am very well aware of what Google is doing. In case, you forgot that:

    <https://play.google.com/store/apps/details?id=de.arnowelzel.android.periodical>


    Basically, most of us are aware Google is adding many (many!) different points of friction such that only the most technical people will sideload.

    Yes, I know:

    <https://keepandroidopen.org/>

    Who do you translated the text for this website to German? ;-)

    <https://github.com/keepandroidopen/keepandroidopen.github.io/commits/main/?author=arnowelzel>

    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.

    No - not "adding". There are just doing it in the future. 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 know exactly what I am talking about since I configured the Gradle
    build for my app in a way to avoid this - even when it is installed via
    Google Play, *all* data is installed, so users can easily switch the
    language *inside* the app, even if their device lanuage is different:

    <https://codeberg.org/askaaron/periodical/src/branch/main/app/build.gradle#L36>

    And yes, F-Droid does *not* use AAB at all, just APK, since they build
    their own release packages.

    And this is the main problem here: in the future Google will NOT allow
    F-Droid packages to be installed any longer by default, because they are
    signed with a key by F-Droid and not by a developer registered at Google
    play.

    And yes, I know exactly about all these issues, because I had to manage
    to get custom versions of PebbleNTN and OpenCamera, which I compiled myself.

    [...]> When this new requirement goes into effect, we will PERMANTLY
    LOSE APPS!
    <https://newpipe.net>

    What's YOUR workaround fix to the permanent loss of those apps, Arno?

    None.
    :: 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.

    So where is the link then to thus "new Google SDK"? Package name?
    Library name? Is it part of AndroidX?

    As does everyone using Muntashirakon App Manager to install their APKs.

    Why don't YOU know about this?

    Because I don't use Aurora Store or "Muntashirakon App Manager" and also
    no apps which need this "new Google SDK". F-Droid does not need it,
    OSMAnd does not need it, OpenCamera does not need it...

    I also never got any information by Google itself as a registered
    developer that I have to add some "new Google SDK" to stay compliant
    with their app store. Have a look at my project - prove me wrong, if you
    find this "new Google SDK" anywhere:

    <https://codeberg.org/askaaron/periodical>

    You always talk from a perspective of end-users. You don't know how
    software development in Android itself works at all.


    --
    Arno Welzel
    https://arnowelzel.de

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Arno Welzel@3:633/10 to All on Saturday, October 03, 2026 11:39:48
    Subject: Re: What, exactly, is Google doing, to copy Apple's anti-consumer sideloading policy?

    Maria Sophia, 2026-10-01 19:52:

    Arno Welzel wrote:
    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. >>
    No - not "adding". There are just doing it in the future.

    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.

    Yes, that was a typo, of course AAB and split APKs.

    And no, this is *not* about "add friction to sideloading"! Just because
    Google Play provides alternatives to a single big APK for distributing
    apps does not mean, it is *intentional* to make sideloading harder!

    These are TWO DIFFERENT DISTRIBUTIONS WAYS!

    Way 1: Provide(!) and use single APK - it's SOFTWARE VENDOR OF THE APP
    who has to provide the single APL - not Google!


    Way 2: Provide your app as AAB using Google Play to optimize the
    download. But again - it is the SOFTWARE VENDOR doing this! Not Google!

    So as a SOFTWARE VENDOR you still can provider single APK - there is NO
    NEED AT ALL to use AAB. So if you want to blame someone, blame the
    vendors providing AAB instead of single APK.

    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.

    They don't. And no I don't like Google either. But you confuse AAB which
    was already invented years ago with the upcoming requirement to register
    a developer account and all apps at Google. Because THEN it will be
    completeley irrelevant if you have single APK or not!

    When Google enforces developer and app registration you CAN NOT SIDELOAD
    AT ALL without using developer options first and wait for 24 hours.


    [...]> I agree that pretty much only Google uses the split APK format,
    which,
    let's be clear, means NOBODY ELSE felt any need for the "value" it brings.

    Not "pretty much" - "ONLY".
    My point?
    There is no value. (practically speaking).

    There is. You just don't see it. My app for example supports more then
    20 different languages. This alone adds a significant of memory
    consumption to the app.

    Some apps contain asset files and code for many different device types.
    Why should all these files get installed on a phone which is not a
    smartwatch or a tablet, nor a device thats supports big XXDPI resources
    anyway?

    Using AAB a developer can separate all the translations, images and
    device specific code into single packages and the device gets only those
    parts installed which it really needs. So instead of for example 500 MB
    of memory, the final installation may only be 300 MB.

    For you this may all sound like bullshit - but imagine a user who has
    200 apps installed and can save 10 GB of memory this way.

    It's a way to limit people from sideloading APKs by adding more friction.

    No, that's a consequence of using AAB, that it can not be used for
    sideloading, since it was not designed for it. But AAB was not designed
    to stop sideloading.

    If it was such a great format, everyone would use it.

    If it was such a shitty format, no on would use it and every software
    vendor would have sticked with single APKs. Why dealing with a new
    package format, when the old works?

    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.

    Google Play can install split APKs.
    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?

    Because it is not part of the Android operating system, but part of
    Google Play Services.

    You must not confuse "Android" and the parts coming from AOSP (Android
    Open Source Project) with "Google Play Services". The one is the
    operating system, the other is a service provide by Google. Also Google
    Maps or Google Camera are not "Android operating systgem" but just Apps
    by Google.

    The point is it's clear to me Google did it for one reason only.
    To add friction to sideloading.

    To me it's clear you don't understand the situation at all.

    The real thread is NOT AAB! It is the enforcement of developer and app registration!

    In the future you will not be allowed to even install YOUR OWN APKs!
    Even APK files you created on your very own with your own computer will
    not be allowed any more without waiting 24 hours after requesting the permission in the developer options! And Google can decide to revoke
    that permission to devices or single apps at any time later because this
    is handled by Google Play Services online!

    So don't bark at the wrong walls and try to understand the real issues here!

    Google's friction being added to sideloading makes some apps impossible.

    WORSE!

    Google will STOP USING ANY APP AT ALL WHICH IS NOT ALLOWED! They will
    remove the apps from their own app store as well!

    [...]>> So where is the link then to thus "new Google SDK"? Package name?
    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.


    "Google Play Integrity" is neither "new" nor "secret". And no, you DO
    NOT HAVE TO DO THIS as developer!

    Some companies MUST do this to be compliant - for example banks often
    add this along with SafetyNet checks to be compliant with data
    protection policies and GDPR.

    [...]
    That friction will be felt by anyone who tries to sideload, do you agree?

    Yes, but you still don't get it, *why* things got invented.


    [...]> Google Maven dependency is simple & yet so very destructive to sideloading.
    For example, a Gradle Android project can declare a dependency like:

    repositories {
    google()
    mavenCentral()
    }

    dependencies {
    implementation("com.google.android.play:integrity:<version>")
    }


    And? Did you find this in my app? And yet my app still is valid for
    Google Play and will be in the future.

    So who is now responsible to add Google Play Integrity checks to an app?
    The software vendor of the app or Google?


    --
    Arno Welzel
    https://arnowelzel.de

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Arno Welzel@3:633/10 to All on Sunday, October 04, 2026 03:49:09
    Subject: Re: What, exactly, is Google doing, to copy Apple's anti-consumer sideloading policy?

    Maria Sophia, 2026-10-03 18:56:

    [...]
    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.

    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.
    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.

    Build and upload an APK file to the developer console and not an AAB file.

    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.

    And you are wrong.

    Just because you can not create copies of apps published on Google Play
    does not mean Android makes it hard to do sideloading in general.

    Technically "sideloading" only means to install apps from a different
    source than Google Play - for example from F-Droid.

    And this is was and is still possible as usual, even after AAB was
    invented. You can take *any* single APK file and just install it. If it
    does not work as expected, don't ask Google - ask the software vendor or developer who provided the APK file.

    F-Droid continued to work as usual, since AAB does not exist there and
    all apps on F-Droid come as single APK files since F-Droid just uses the standard package format for Android which was not changed at all.

    If your beloved apps will only be distributed on Google Play, then you
    have to live with the consequences.

    Please stop confusing "copy apps which are only distributed on Google
    Play other app stores and try to install it from there" with "sideloading".

    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.

    The creators of Android did create APK - hence the name "Android
    Package", APK. And no, Android was not created by Google originally,
    they just bought it and continued the development.

    Nobody adopted the split-APK format.

    Nobody creates a "split APK" to distribute an app. You create an AAB -
    and Google Play will then build a "split APK" based on this when the AAB
    is uploaded there.

    1) The AAB gets created in Android Studio using Gradle.

    2) The AAB gets uploaded to the Google Play Developer Console.

    3) Google Play will create "split APK" for downloding in the Google Play
    app.

    The is no way to create a "split APK" in the first place in Android
    Studio with Gradle. This is just the result of using AAB for
    distributing an app via Google Play instead of APK. But if you devide to
    use F-Droid for distribution, you don't even have to build an APK at
    all, just give F-Droid the URL of your git repository and they will
    create new single file APKs on their own, as soon as there is a new
    release tag in git.

    [...]

    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 .

    I don't. But I do not agree that backup, transfer and restoration of applications is very useful.

    When you use Linux you also wouldn't back up all existing programs to be restored somewhere else. Of course you would reinstall the software if
    you want to use a new computer and only restore your *data* and
    configuration as needed. The last time, that I backed up most of the applications that I installed must have been more then 15 years ago.

    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?

    Because Google Play Services including AAB and "split APK" are
    proprietary closed source binaries and *not* part of Android, which is
    open source.

    And when I talk about Android as open source system, I mean this:

    <https://source.android.com> <https://cs.android.com/android/platform/superproject>


    --
    Arno Welzel
    https://arnowelzel.de

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Arno Welzel@3:633/10 to All on Monday, October 05, 2026 13:31:09
    Subject: Re: What, exactly, is Google doing, to copy Apple's anti-consumer sideloading policy?

    Maria Sophia, 2026-10-04 04:57:

    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.

    I AM!

    You already forgot, that I did the translation of
    <https://keepandroidopen.org> to German?

    You already forgot, that I am a software developer also writing stuff
    for Android apps for many years now?
    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.

    Except you can still enable sideloading - it's just a cumbersome
    process. See <https://keepandroidopen.org/>.

    [...]

    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>

    This information is just wrong. Yes, Google asks to upload AAB since
    2021, but in reality APK still works.

    [...]>> Just because you can not create copies of apps published on
    Google Play
    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.

    That means, you will struggle to "sideload" these copies.


    Rest ignored - it's not worth my time any more really...



    --
    Arno Welzel
    https://arnowelzel.de

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)