-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Google will block side loading apk at 2026
- Thread starter incendio
- Start date
- Similar Threads Similar Threads
TL;DR:
No, Google isn’t blocking all APK installs outside the Play Store.
What’s changing is that starting September 2026, developers must register with Google (ID verification) and register their apps (signing keys + package names) so that users will be able to sideload your apps onto their "google certified" devices (devices that have google play services on them).
The exception: APKs can still be installed via ADB without registration, but that won’t be practical for most end users.
No, Google isn’t blocking all APK installs outside the Play Store.
What’s changing is that starting September 2026, developers must register with Google (ID verification) and register their apps (signing keys + package names) so that users will be able to sideload your apps onto their "google certified" devices (devices that have google play services on them).
The exception: APKs can still be installed via ADB without registration, but that won’t be practical for most end users.
Last edited:
Does it mean developer must have a developer account?
In the near future Google will open a special registration portal (separate from play store) for non-play store developers to register their apps.
Last edited:
Depending on the actual details, it might affect B4A-Bridge. USB debug mode is using ADB under the hood.
Would it be possible for B4A to transition to using ADB's wireless debugging feature?
It’s very likely that this “registration check” will be tied to a Google Play Services update. That means it won’t technically depend on your Android version, but rather whether your device still receives Play Services updates. If your device gets the update, the new policy could apply regardless of the Android release it’s running.
That said, there are still some big unknowns:
- Existing apps – If you already have an unregistered app installed, will it be allowed to remain on the device, or could it be blocked/disabled after the policy goes live?
- When the check happens – Will the registration check run only during installation, or continuously in the background? If it’s at install time, is it a local lookup against a database updated through Play Services, or will it always need a live connection to Google’s servers?
Last edited:
Any chance of Basic4Browsers? eg Javascript seems to have access to GPS, accelerometer, gyroscope, and BLE, so that's everything I ever use. No wait, I use Classic Bluetooth for serial link to OBD2 interfaces too. Then again, I vaguely remember that iOS is super-restrictive about Bluetooth SPP, so perhaps everybody's moved to serial-over-BLE by now.
Where my thinking was headed is that maybe this clamping down on native apps might end up backfiring on our don't-be-evil friends by driving developers and users towards solutions that are less straight-jacketed.
Where my thinking was headed is that maybe this clamping down on native apps might end up backfiring on our don't-be-evil friends by driving developers and users towards solutions that are less straight-jacketed.
Last edited:
Maybe. As @JohnC wrote we need to wait for the exact details and understand the implications.
Hi, good morning, afternoon or nights 
Some year ago I did a small test development in a framework called Ionic, it is like an embeded web browers and pages, pages are like webpage (you have code these pages using several web languages like javascript , angular, react, etc). It was very limited about using device hardware at that time (serial, bluetooth, gps) and you have to master several programing techniques. However because app run in browser you dont have a real apk to register. Maybe this method could be an alternative for google mess up.
After this experience I conclude B4X suite is the best, fast to learn, fast to code and fast to mantain code.
Best Regards
Some year ago I did a small test development in a framework called Ionic, it is like an embeded web browers and pages, pages are like webpage (you have code these pages using several web languages like javascript , angular, react, etc). It was very limited about using device hardware at that time (serial, bluetooth, gps) and you have to master several programing techniques. However because app run in browser you dont have a real apk to register. Maybe this method could be an alternative for google mess up.
After this experience I conclude B4X suite is the best, fast to learn, fast to code and fast to mantain code.
Best Regards
My understanding from the information I received is that even if you distribute apps outside of Play Store, you'll need to create an Android Developer Console account:
https://developer.android.com/developer-verification/guides/android-developer-console
I also suspect that there will still be a way for users to side load unregistered apps, otherwise there would be a significant backlash. My guess is that it will be something along the lines of the current "unknown source" blocking that can be bypassed by the user.
I already write to google support forum, many user are concern about small sample test apps, they said you can still load these apps using ADB, however discussion is open on that forum.
I think a Basic4Browsers , that would be really great, to complete the B4X suite
Not sure if this is what you need, but I'm currently using wireless debugging with B4A. I start the adb connection from the PC to the Android device and then everything works in the IDE like when the device is directly connected over USB. For me is a must as I cannot connect the Android device to the PC over USB and use some USB interfaces in the same time. B4A-Bridge has some limitations (ask for permission each time I install the app, is slower and Take Screenshot does not work for me).
I never thought about this and I just tried this out and my mind is blown. No more Google Play Protect nagging