this post was submitted on 16 May 2025
427 points (97.1% liked)
Technology
70248 readers
3516 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Except Google is trying to limit this on Android phones as well (e.g. with SafetyNet).
If manufacturers had their way, there wouldn't be any phones for one side.
There's nothing stopping manufacturers from permanently locking the bootloader. Some do and others don't suggesting that the industry does not have a universal preference.
I do think Google wants it to be inconvenient enough to run a version of Android they haven't blessed as one's main phone that it has no chance to become mainstream, but that's about the prospect of an OEM not bundling Google's apps and store, not hobbyists running custom builds. If that sounds like an attempt to use market power to exclude competitors in violation of fair trading laws in a multitude of jurisdictions, you might be on to something.
Some manufacturers have stopped allowing unlocking their bootloaders, some bootloaders have been hacked by the community. It's not like this is a static system.
No, Google is also trying to stop hobbyists running custom builds from accessing services built on their software (the aforementioned SafetyNet). Hackers keep finding ways around this, but Google keeps trying to lock them out.
That's a side effect. If Google really wanted to interfere with hobbyists, they would mandate hardware-based attestation and all the current workarounds would be broken. It would be much harder to create workarounds for that.
And also all current phones would be broken, which they can't do.
It appears phones as old as the Android 8 era can support this and phones that shipped with Android 13 or newer always do. I had the impression it had been universal a little longer.
I mean that's something that'd happen regardless of whether you may install other App Stores on an iPhone easily, no?
GP wrote:
App stores are just one part of the puzzle. Unless consumers actually have rights, manufacturers will keep trying to limit their options.
The reason I don't use Android phones in China is because every company uses its own, separate version of what's basically microG (notifications, location...) and update checking, and so my RAM is gone before I know it and everything's super laggy. And on my grandma's Android tablet these desktop-style notifications pop up overwhelmingly because of certain apps that bundle adware. This is what happens when sanctions took away a default option. Customization is no doubt something great for hobbyists and an option that should exist but there is a benefit to having a default monopoly (though, again, there should be an opt-out).
Sure, but Google is trying to take away that opt-out! So we'll be left with a monopoly and nothing else. That's strictly worse than not having a default monopoly.
I agree with you, but my point from the start here (which I should've said more clearly) was that this doesn't mean Apple must open up in response (and by default), which would leave us with no good centralized, minimalistic option either.
But you don't have Google available as an option due to sanctions, right? It doesn't have anything to do with other options being available. The same would go for Apple - they could be cut away with sanctions, and having other options wouldn't preclude the default option from existing.
I don't get what you mean.
How do other app stores on Android lead to Google stuff not being available? There's no connection, the reason is sanctions.
How would other app stores on iOS lead to Apple stuff not being available?
I'm not saying having other app stores on Android nor iOS lead/will lead to them being unavailable. I'm saying there needs to be an option with a single app store and set of services. Having multiple app stores on Apple and very easily installable would cause similar issues with RAM and usability for the less initiated, and everyone was uninitiated once.
Other app stores on Android don't necessarily lead to issues with RAM and usability. They don't have to re-implement the Google framework stuff.
The same would go for Apple, and people will simply have options. Sure, they'll have to learn about them, but they have to learn about many things in life! And it's not like Apple will suddenly allow others to re-implement their SDK.
But there's no reason to discuss hypotheticals here, as this is currently playing out in the EU. We should be seeing the issues you mention, but we don't.
Most of these apps don't in China either. But you do need to reimplement an update-checker. And that's enough to hog the RAM. And with the RAM already hogged, the window shattered, little optimization of the update-checker is done.
They won't learn about it if it becomes the norm to have RAM hogged.
No, you have to go through complicated bureaucracy and fees to become an independent app store for iOS. Anyone who goes through this is probably competent enough to optimize their update-checker.
I have three app stores installed on my Android, yet none hog my RAM. This is a non-issue (especially since an update checker doesn't run all the time, only on infrequent intervals which are triggered by the OS itself).
You are initiated enough to consciously avoid junk apps.