HNHacker News
TopNewBestAskShowJobs

rejhgadellaa

134 karma · joined September 1, 2021

submissionscomments
rejhgadellaa··on Apple's intentional crippling of Mobile Safari
But on macOS you can switch to a browser that can do all these things. A company could ask you to use a different browser (not ideal, but if the web app requires a specific API, it's not an unreasonable).

Safari is in a very special position because it controls what the web can do on iOS (all browsers on iOS have to use Apple's WebKit engine, they can't add web features). Apple is not just gatekeeping native (through the app store), but its competition, too (the open web, through the webkit requirement)

rejhgadellaa··on Don't Download Apps
Not entirely true. Browsers are paranoid by default (because visiting a website is as easy as clicking a link). Operating systems aren't (because the user explicitly installed an app, it's been "vetted" by app store experts, and because... well, the OS vendor wants you to build native apps and not a website, so they have to make it worth the extra trouble of building a separate app for each platform instead of one website that works everywhere).

Also, browsers tend to bring their own sandbox (on top of what the OS already does). For example, Chromium was able to mitigate Meltdown/Spectre before OS vendors shipped an update (except on iOS where browsers can't bring their own engines, so iPhone users had to wait for Apple to ship an OS update...)

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
Yeah so native apps have some unique abilities to track you that websites do not.

On top of that, platforms like Reddit and Facebook tend to prefer native apps because it's easier to keep you within the app. Even if you click a link to an external website, for example, Facebook will open that link in an in-app browser (unless you find the opt-out). A few years ago, a researcher found out that these apps often inject their own javascript into that in-app browser. In theory, that means FB can track you even on external sites, even if you do not accept cookies for that website. You just brought your own tracker. Facebook then decided they should ship their own entire browser engine, giving them even more control.

https://webventures.rejh.nl/blog/2022/in-app-browsers-are-tr...

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
I'm afraid it's the other way around. Browsers are (generally) better at sandboxing than OSs. Browsers are paranoid by default. They have to be, because visiting a website is just a click away (compared to multiple clicks/taps to install a native app).

For example, Chromium was able to mitigate Meltdown/Spectre within days, even if the OS was still vulnerable. (Chrome already had site isolation ready to ship, a feature that completely isolates websites into their own process). Even better, Chromium browsers tend to update themselves (or via Google Play) automatically.

Meanwhile, OS vendors were scrambling to ship an OS update.

(Also, worth mentioning that iOS users were vulnerable until Apple shipped an OS update, because every browser on iOS has to use Apple's WebKit)

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
> If it were just a website, you wouldn't have a little picture of their logo on your phone

You can install web apps on the home screen since iOS 1.0. The fact that you (and many, many others) don't seem to know this is a thing, says a lot about how effective Apple is at hiding that feature... :(

(Chromium browsers support an API where a website can show an install button if certain conditions are met, making it a one-click experience. But alas, for some reason Apple doesn't allow browser engines except the one they control :thinking: )

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
100% agree. Except it would be nice to have a notification, reminding you that the meter is running. And on iOS, you need to install a web app before it can send notifications, defeating the point of not having to install anything.

https://webventures.rejh.nl/blog/2023/ios-web-push-requires-...

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
If the website is a PWA, it can be installed to the home screen and look and behave just like a native app. You just tap the icon on the home screen. It will remember your login.

And the upside is that you only have to develop one website (instead of a website and 2 separate native apps for iOS and Android).

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
Then why did you switch (honest question, not intended to be snarky)?
rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
Contacts Picker API: https://developer.mozilla.org/en-US/docs/Web/API/Contact_Pic...

Hardware APIs: There is of course a good reason why websites don't get unlimited access to those APIs (and why they can't access them in the background). But Bluetooth and USB are both available on Chromium browsers on every platform except iOS (because Chrome on iOS is Safari).

Example: When Google closed down Stadia, they offered a way to unlock the Stadia controller so you could connect it via BT to any computer and use it as a regular controller. You just went to their website, hooked up the controller via USB, and the site would update the firmware on the USB device.

But sure, there are many use-cases for native apps. Also, there are many native apps that should just be a website (you shouldn't even need to install it if you only need to use it once or twice).

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
A website can work offline, too. Service workers are a feature that any website (installed or not) can use to (pre)cache assets, etc. On iOS, that data will get evicted if the user doesn't visit the site at least every 7 days, though. Other platforms keep the data for a lot longer, but will evict at some point, too.
rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
Part of the problem is that the websites need to "share" budget with the teams that build 2 separate native apps (or maybe they use something like React Native, but that still costs money that could've been used for a better mobile website).

Also, if a company has a mobile app, a bad mobile website is less of a problem. Take Takeaway.com. Their mobile site is terrible. But they have a pretty good mobile app, so why would they need to pour money into making the site any better?

But yes, (mobile) web also just needs to do better.

rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
I meant to say "Every regular website can have a service worker", but can't edit anymore
rejhgadellaa··on App Should Have Been a Website (and Probably Your Game Too)
Service Workers do not require an installed PWA. Every regular website can have a PWA. I'm not sure who came up with this explanation for Apple trying to kill PWAs in Europe, but it makes zero sense.
rejhgadellaa··on An Abridged History of Safari Showstoppers
TL;DR: iOS Safari is more than an inconvenience for developers, it's the fundamental reason interoperability has been stymied in mobile ecosystems; frequent showstopping bugs, a large patch gap, and lack of competing engines ensures the web is not a credible competitor to native. Here are the receipts to prove it.
rejhgadellaa··on Apple reverses course on death of Progressive Web Apps in EU
Yep that was a mistake. Thank you!
rejhgadellaa··on Apple reverses course on death of Progressive Web Apps in EU
Nowhere in Apple's statement or anywhere else does it say that the EU agrees with this. It's just Apple announcing a plan. I can imagine them being like "we showed we'd be willing to kill PWAs entirely, so they surely will be OK with our olive branch here and let us keep our WebKit restriction in place for PWAs"

But I'm not so sure. I certainly don't hope so.

The EU isn't stupid. They very much capable enough to see Apple's shenanigans for what they are.

rejhgadellaa··on Apple reverses course on death of Progressive Web Apps in EU
The law requires Apple to open up iOS to 3rd-party browser engines and that Apple can't self-preference their own browser. This would mean that Apple has to open up anything that Safari can do (like run PWAs).

I don't believe for a minute that the EU is OK with the WebKit restriction here, they simply haven't responded: https://news.ycombinator.com/item?id=39565553

rejhgadellaa··on Apple reverses course on death of Progressive Web Apps in EU
To anyone reading this as "the EU is okay with PWAs being restricted to Safari/Webkit":

(I've seen a couple of those comments go around here on HN)

I don't think so. Nowhere in Apple's announcement does it say "the EU is okay with this".

What Apple has announced today is a(n update to their) plan to comply with the DMA. The EU won't actually do anything until March 7th (the deadline for compliance). The fact that they did do something following Apple's announcements regarding PWAs just shows how obviously ludicrous those plans were. The EU recognized the urgency of the situation and acted [1] - If Apple would have shipped this update, many existing PWAs would stop working overnight, those apps would jump ship and offer their PWA in the App Store with (no way back?) and the damage to the reputation of PWAs would have been done: Apple would've sent a message that you can not rely on the web to reach your customers on iOS.

Nowhere does anyone say that the EU is OK with PWAs being restricted to WebKit. In fact, the DMA demands the opposite: Apple has to open up iOS to 3rd party browsers, and Apple can't self-preference Safari/WebKit for any of its features. Like, say, run PWAs.

I have read lots of comments and posts that said something along the lines of "Apple doesn't want other browsers to run Service Workers". That's not the reason for the attempt to remove PWAs on iOS. Service Workers are not PWA-only, every regular website in a browser tab can have a Service Worker. PWAs can be added to the home screen just fine without one. They are not mutually exclusive.

Apple removed PWA support so they would not have to open up the APIs to other browsers. Period.

So, to circle back to "the EU is okay with PWAs being restricted to Safari/Webkit":

I very much doubt it. Apple has announced a plan to comply, forgot to mention they were going to kill support for PWAs, then did confirm it (only took them 2 weeks), and now they backed down. We're back where we left off a month ago - and I believe the EU is very much going to have an opinion on the WebKit restriction Apple is trying to keep in place.

[1] The EU only announced they would start an investigation AFAIK, which is a long way from actually enforcing anything.

rejhgadellaa··on Apple reverses course on death of Progressive Web Apps in EU
Service Workers (SW) and installable PWAs are two different things.

Regular sites in browser tabs can have SWs.

When the full Chrome(ium) or FF hits iOS (engine and all), they will want to run SW. And, if I understand the DMA correctly, Apple will be forced to make that possible for 3rd party browser engines.

rejhgadellaa··on Apple Attempting Killing PWAs in EU: Immediate Action Needed
Oh boy answering that is going to take a while. For now, this post should cover what Apple's trying to do: https://open-web-advocacy.org/blog/its-official-apple-kills-...

And if you really want to know what it's all about, this covers... all of it? https://open-web-advocacy.org/walled-gardens-report/

rejhgadellaa··on Browsers are the most likely disruptor of the mobile duopoly
Hmm I would hope that the richest company in the world could build a better browser than anyone else and market it like no one else.

Except they didn't. Apple relied on their browser ban on iOS, on users not being able to set a default browser for 14 freakin' years.

Sorry, this is their own fault. Safari could be competitive, but if it turns out it isn't, it's on Apple and no one else.

rejhgadellaa··on Apple attempting to stop investigation into its practices involving browsers
> The Safari team seems to be well-funded [...]

Meh. Safari is owned by Apple, the richest company in the world and they're beaten by a non-profit(!) who spends ~500 million / yr?

Apple only started properly funding Safari and catching up with Firefox and Chrome when regulators started looking into their practices.

rejhgadellaa··on Apple attempting to stop investigation into its practices involving browsers
Any app you install downloads megabytes worth of code, assets, etc. That's all local storage.
rejhgadellaa··on Apple attempting to stop investigation into its practices involving browsers
Oh come on, relying on local storage is not the same as not having a backup.

Modern web apps can cache all the files they need to function. They can work offline. So when iOS deletes a web app's data, it doesn't just delete some content and maybe a few settings. It's basically like it deletes the entire app and you have to reinstall it (by opening the web app and re-download all assets that make it work). Sure, the icon is still on your home screen, but the entire app behind it is gone.

It'll also delete things like your login status/tokens/etc, so you have to log in again, maybe the web app has settings that it doesn't want to sync across devices, etc.

I assume that when Web Push hits iOS, notifications will only work as long as you open the web app often enough.

rejhgadellaa··on Apple attempting to stop investigation into its practices involving browsers
For anyone making the "Apple is the last bastion against Chrome dominance"-argument: Apple is not in it for the web. Quite the opposite, more likely. They are all about control, not letting you choose a browser.

Also, I don't see how fighting a potential monoculture with an actual monoculture is a solution.

For further reading: https://infrequently.org/2022/06/apple-is-not-defending-brow...

rejhgadellaa··on Apple attempting to stop investigation into its practices involving browsers
You couldn't set any if these alternative browsers as the default until fairly recently. That ensured their market share was kept to a minimum and people have gotten so used to Safari few people find it worth switching now.

Also, Safari has some super powers compared to the others on iOS (things the other browsers are simply not allowed or even able to do like Add to homescreen)

rejhgadellaa··on Apple’s browser engine ban is holding back web app innovation
Which features are we talking about? Bluetooth? NFC? Contacts? Because native apps enjoy all of them, AFAIK. These same features tend to have extra protections built in that native apps do not to ensure privacy and security. The web is extremely paranoid when implementing these features.

From what I've learned, WebKit is not engaging in discussions regarding these new features. They could have a say in shaping the web, come up with alternatives, new features, etc. Instead they dig in their heels.

If Safari needs "the requirement of iOS users using it" to hold back Chrome, it tells us people actually want to switch.

Letting Apple decide what's best for us (for reasons that have nothing to do with "what's best for us", I think is safe to assume) is not the solution for the monolith browser problem we're seeing.

rejhgadellaa··on Apple’s browser engine ban is holding back web app innovation
We don't really know if there's going to be a hit on battery life because we've never been able to test this (since there are no alternative browsers to test with).

Besides, you should be able to keep using Safari and the impact will be exactly zero :)

rejhgadellaa··on Apple’s browser engine ban is holding back web app innovation
So.. you're saying you can use (pure) Chromium or Brave, Edge, etc, to test, right?

Not sure what your point is, because you're immediately saying you know there are alternatives :)

rejhgadellaa··on Apple’s browser engine ban is holding back web app innovation
> None of the arguments about battery life, security, or privacy were contradicted in this article.

Regarding battery life, and to quote your own remark, one line below this:

"There's no evidence that that is true, nor has there ever been." - because no other browser was ever benchmarked / tested because there is no other browser.

Regarding security: Having one single attack surface for every single iOS user is not "good security". If Safari/WebKit has a problem, every iOS user has a problem and they can't (temp) switch to an alternative. To fix it, Apple needs to roll out an entire OS update, 15 minutes downtime, reboots and all. And users tend to postpone OS updates because of it.

Regarding privacy: You're saying Safari is better at privacy than Firefox, Brave, etc? We don't really know, do we?

Actually, Safari on iOS has privacy / security features that Chrome, Firefox and others on iOS do not because they can't access the necessary APIs. Apple is actually undermining user privacy and security here.

← PreviousPage 2 of 3Next →