You still can do that with PWAs in Android. Let's see for how long.
And I wonder when can we stop lying to ourselves pretending "web"-apps are real (native) apps?
Googles/Apples argument would have been much stronger if their stores managed to not allow scams/malware/bad apps to their store but this is not the case. They want to have the full control without having the full responsibility. It's just powergrab.
I think they’re just going to track down a random person in a random country who put their name down in exchange for a modest sum of money. That’s if there’s even a real person at the other end. Do you really think that malware creators will stumble on this?
This has to be about controlling apps that are inconvenient to Google. Those that are used to bypass Google’s control and hits their ad revenue or data collection efforts.
Do that + identity check = bans for virus makers are not easily evaded, regardless of where they live.
The iPhone 17 is the same price as the Pixel 10
> better
But the iPhone 17 has better hardware features, like UWB, better cameras, and a _far_ faster CPU.
> open source
Only if you install Graphene, and then never install anything that requires Google Play Services, which is basically every commercial app.
Given that Google both owns Android/Google Play Store and YouTube: what do you think they would do with the developer information of someone who makes an app that skirts their ad-model for YouTube?
Scam apps are rife in the iOS App Store. But what they can’t do easily install viruses that affect anything out of its sandbox, keyloggers, etc
2. I think it's better, I like the UX but that's subjective.
3. Not open source. AOSP is open source. Android is not open source.
“In 2024, the App Store made $103.4 billion to Google Play’s $46.7 billion.”
I agree let's have sandboxed app instalations on platforms. Flatpak is already going this way. But it looks like big players Microsoft,Apple and Google are gatekeeping app sandboxing behind their stores instead of allowing people/devs to use sandboxing directly.
The "security" wording is the usual corpospeak - you can always trust "security" to mean "the security of our business model, of course, why are you asking?"
No longer true with the newest chip that Mediatek cooked up, ARM licensed cores like C1 are catching up rapidly with Apple CPUs (or maybe Apple has hit the limit of their current design philosophy)
The fact that there was a temporary workaround didn't change the endgame.
It's just there to boil the frog more slowly and keep you from hopping out of the pot.
It's the same game plan Microsoft used to force users to use an online Microsoft account to log onto their local computer.
Temporary workarounds are not the same thing as publicly abandoning the policy.
I, too, love vendor lockin.
It’s utterly bizarre how BBM could have been the iMessage and WhatsApp and who knows what else. But rich out-of-touch people thinking exclusivity is a perk in a commodities market just shows how business savvy and wealth are in reality disconnected from eachother.
Is that really your answer? To make the phone ecosystem as fraught as Windows PCs for the average user? How is they worked out for PC users since the 80s?
The only Android phones that are significantly cheaper than equivalent iPhone tend to come with some kind of compromise (and don’t forget that Apple’s phones start at $600 - the iPhone 16e exists).
https://grapheneos.org/features
>GrapheneOS is a private and secure mobile operating system with great functionality and usability. It starts from the strong baseline of the Android Open Source Project (AOSP) and takes great care to avoid increasing attack surface or hurting the strong security model.
It is still unbelievable to me that Google is shipping a product which takes 10 seconds to show anything when I search through my phones settings. What are they doing?
>open source
Sure. If you buy the right phone you get some open source components. Of course half the Android companies are trying to funnel you into their proprietary ecosystem as well. The rest just wants you to use Google's proprietary ecosystem.
0 - https://discuss.grapheneos.org/d/16046-google-keyboard-w-net... 1 - https://discuss.privacyguides.net/t/sandboxed-google-play-pr...
Things like Newpipe seems much more of a target, especially if you want to take legal action. More so than stopping users, this gives Google fat more leverage about what Apps can exist. If they ever want to stop Newpipe a serious lawsuit against whoever signed the APK seems like an effective way to shut down the whole project. Certainly more effective then a constant battle between constraining them and them finding ways to circumvent the constraints.
For vast majority, Android vs iPhone is not massively different so iMessage availability is a draw for some people.
I had been thinking for a long time to switch to Android (GrapheneOS, probably) when my current iPhone 13 dies, but this whole thing with "sideloading" on Android is making me reconsider. If I can't have the freedom I want either way, might as well get longer support, polished animation and better default privacy (though I still need to opt-out of a bunch of stuff).
I doubt they learned their lessons. Apple walked all over them in so many ways and, if memory serves me right, they even mocked Steve Jobs over the iPhone.
Edit: just so I’m clear I’m discussing it from the perspective of early to mid 2000s. iPhone hadn’t yet come out, but iPods were popular. Trillian and Pidgin were dominating the online landscape of software that could support multiple chat protocols - seamless ICQ, AIM, IRC, Yahoo, MSN Messenger, all in one program. If there was a time for RIM to corner the market here it was right then and there because BBM was the real deal, being available on phones and they could have signed agreements with others to bring it to, for example, Nokia and Motorola and whoever else.
But no. They’d rather be arrogant and stupid.
Also, with this move, Google has made it very clear that they don't want people to have any real control over their machines -- so I'm not inclined to think that using adb to work around the problem will always be possible.
It's fine, though. My hobby projects will continue into the future, just probably without using Android.
But you'll be reminded quickly how comparatively shit Apple's software is.
Aka the litany of "Oh, yeah, everyone knows that's broken but just deals with it, because there's no way to fix issues on a closed platform other than {wait for Apple}."
https://www.androidpolice.com/use-wireless-adb-android-phone...
I make lots of "real" healthcare apps that are PWAs.
Much better installation and user experience, no dev cert nonsense, brain dead simple updates, no app store, etc...