Android’s new 24-hour sideloading delay should’ve happened years ago


Sideloading is a hot topic in the mobile sphere, and Google recently made a huge change for how it works on Android. I think it’s a fantastic change, and I wish Google would have added the 24 hour delay for sideloading unverified apps years ago, but I’m glad they’ve finally done it.

The majority of people don’t actually need to sideload apps on Android

The squeaky wheel gets the grease

An APK icon next to a smartphone with a padlock between them. Credit: Lucas Gouveia / How-To Geek | Maor_Winetrob / Shutterstock

If we’re being realistic, the average person doesn’t need to sideload an app. I’ve gone nearly a decade without even desiring to sideload an app on my iPhone, and even the past few years that I’ve had an Android device as a secondary system, I haven’t wanted to sideload an app on it.

The thing is, sideloading apps is a very niche topic in the world of Android—but the vocal minority love to scream about how big of an issue it is. I get it, being able to sideload is a nice feature, but it’s not actually a necessity for most people.

I have family members who have had Android devices for many, many years, and they’ve never sideloaded anything. I’ve talked to other people out and about and they don’t even know what sideloading is.

I feel like Google has listened to the vocal minority for far too long on sideloading, and I am very glad that they’re finally taking steps to make it a bit more difficult to sideload apps.

Sideloading is nice, but it’s typically not an urgent need

Waiting a day isn’t the end of the world in most non-developer cases

I’ll admit, I have definitely sideloaded apps many times. I used to do it all the time, and now it’s only on a very rare occasion. However, I can count on zero fingers how many times that need to sideload has been urgent.

The vast majority of sideload needs on Android also aren’t urgent. Maybe you want to play Fortnite and need to sideload the Epic Games Store—that can wait until tomorrow. Or, maybe you’re trying to load an older version of an app? That’s also not urgent.

With Google’s new 24-hour waiting period to sideload apps, the average consumer simply has to wait a day before they can sideload the app.

However, the 24-hour delay only applies to one specific segment of developers: unverified developers. If an APK comes from a verified developer, then it can still be sideloaded without waiting 24 hours. Also, if the APK is sideloaded via ADB on a computer, then it bypasses the 24-hour delay as well, meaning if you do have an urgent need to sideload an APK, then you can just do it over ADB.

Locking sideloadind behind a 24-hour delay will help more people then it hurts

It’ll stop hackers in their tracks when Grandma can’t sideload a cracked APK same-day

Android robot standing on a laptop keyboard with code running on the laptop screen. Credit: quietbits/Shutterstock.com

So, why is Google even making this change? To help prevent people from being packed. In the past, hackers have distributed malware-riddled APKs to unsuspecting people to download and install. The tactics are varied, but the delivery mechanism is the same.

So, by Google making it so you can only sideload verified APKs by default, and you have to wait 24 hours to sideload an unverified APK, they aim to reduce the amount of scams.

Getting verified on the Play Store is cheap and easy—it only costs $25 and takes a few minutes to apply, then a day or two to be approved. I did it a few weeks ago and it was a simple process. Any real developer is going to take the time to get verified and properly sign their APK. If a verified developer distributes malware, they likely won’t be verified for long, meaning their APKs would fall under the 24 hour delay.

Pixel 10 Pro

Brand

Google

SoC

Google Tensor G5

The Pixel 10 Pro offers an upgrade over the base model with the powerful Google Tensor G5 chip, more RAM, and more storage (if you need it).



Google isn’t taking away your ownership by making you wait 24 hours to sideload an unverified APK

I get the arguments that people are making that Google is taking over their device and not letting you use it as you want, but that’s simply not true. Google was very strategic with the sideload delay, making it only affect unverified developers. The fact that Google left ADB wide-open to sideload immediately goes to show that Google isn’t trying to reduce functionality or take over your device, but simply protect people from sideloading something that could harm their device.

I think it’s long overdue for Google to step up and take protective measures for its users, and I’m glad that they’re finally doing it. I also like the way in which they did it, not taking features away from people, but simply adding in a small hurdle that will make it more difficult for hackers to trick people into giving them access to their device.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


For years, location permissions have been a bit of a mess on Android. You open an app, it asks for your location, and you’re suddenly making a decision: While using the app? Always? Precise? Approximate? Most of us just tap something and move on, half-aware that we might be sharing more than we need to. With Android 17, that finally changes. It shifts the decision to the exact moment you actually need it. This actually changes everything.

The new location button keeps things simple

The new feature is called the location button. Instead of handing over your location to an app indefinitely, you now get a simple, dedicated button for it. Let’s say you’re trying to find a café nearby. You tap the button, the app gets your precise location for that moment, does what it needs to do, and that’s where it ends. It also reduces those annoying permission pop-ups. Once you allow access for that particular action, the app does not keep asking you again and again.

And if you are someone who occasionally wonders, “wait, is something tracking me right now?”, this update will feel reassuring. Android 17 introduces a persistent indicator that shows up whenever an app, not the system, is using your location. You can tap it to instantly see which apps have recently accessed your location, and revoke permissions right there if something feels off. There is also a thoughtful upgrade to how approximate location works. Earlier, Android used a fixed grid to blur your location, which was not always as private as it sounded, especially in quieter areas. Privacy should not depend on where you live, and this finally feels like a step in the right direction.

Permission prompts that don’t feel like a test anymore

The old permission dialogs could be confusing, to say the least. Android 17 gives them a fresh redesign, making options like Precise vs. Approximate location much easier to understand.

The update also gets something important: not every app needs to track you all the time. Sometimes, you just want to share your location once and move on with your day.



Source link