What features on the browser are blocked that are preventing your app from being a PWA? Is it one of the many Google supported privacy breaking features no other vendors want to implement?
There are all kinds of small issues. For example, we can't do HDR on iOS for photos in the browser because WebGPU doesn't support it.
Apple is on the W3C comittee that gets to decide on which proposals will become standardized browser APIs. And they use their power there to block API proposals that could make browsers more capable, competing with native apps.
Apple is holding up quite a few useful API proposals, and they won't even suggest any changes to make to the proposals. They just do not want web browsers to be any more capable than they currently are. Apple is literally stifling innovation in favor of their own greed.
It seems odd the world is letting one company hold our hand behind our backs.
The only reasons I see Firefox blocking it is 1) Apple is paying them, 2) Firefox just doesn't have the resources to implement them. I'm leaning towards option 1, because Firefox shouldn't care what other browser makers have the resources to implement as long as the API proposals are sound (and they are sound).
Edit: If you're going to downvote, at least provide a comment as to why I'm wrong about any of this. Provide some evidence that counter my statements. I admit I stated opinions, not facts.
Apple only allows you to access the microphone if you use HTTPS so I had to use Tailscale serve to get a url and I use that.
Distribution is tricky since you’re asking a person to run a web app but fuck Apple’s walled garden.
For my personal OS, the main app is one where I can control terminals on my Mac on a web page and I built that into the personal app. The other is a calendar that’s not connected to Google or Apple calendar. It has an MCP so Claude can schedule tasks for me, workout session, LinkedIn posts, etc. It has a nice timeline so I can see my day.
Another big app is curator where I started finding and collecting nice things I find on the internet and good websites. Overall it’s a great playground to get ideas off the ground before turning them into fully fleshed products.
I also made a lot of mini apps in personal OS for websites I don’t like or push ads so I use their unofficial API. It also has a built in web browser in the web app itself so I can look at the website changes and dictate to the AI at once. Overall it’s helping me build an open-source Shopify for every vertical.
My one suggestion is to create a style guide for Claude so that the homepage doesn't have Claudeisms.
For example, Claude loves the word hold, which is v annoying. The word "with" is right there.
E.g. "anyone holding its invite link"
To keep Safari relevant.
> At the surface level this just seems silly so I must be missing something.
I worry a lot about the day Chrome becoming possible on iPhones, because at that point, people will be able to ignore Safari.
(the nag likely varies by region, time of day, your browser extensions, operating system, and moon alignement so ymmv)
If users didn't pay enough attention while clicking next through the installer, they ended up with Chrome as their default browser without understanding how that had happened.
This behavior is disallowed on the App Store, and nobody is asking for that policy to change, but of course Apple, Google, and the Android OEMs can use their privileged position to bundle apps with the OS.
https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
E.g. despite repeatedly getting "use safari/default browser" all Google apps will ask you again, and again, and again, and again, "Open in Chrome (default choice), Safari, System browser"
You might not consider that magic, but I do: Look how it changes absolutely everything about what you said without you needing to change a single word.
I recently had to install Chrome (Chromium wouldn't cut it) on my Mac laptop to do a Telehealth call. That and Edge (which is also Chrome, though that wasn't enough for Chromium to be allowed) were the only two browsers it'd permit, Safari, Firefox, and Chromium (I had all three already) were all refused. That horse-shit would be all over iOS too, if more browser engines could run on it.
On the one hand, they may have self-serving reasons for not permitting other browser engines on iOS. On the other hand, I'm very glad they do it for my own selfish reasons.
Yet…
https://www.gov.uk/government/publications/mobile-ecosystems...
But hacker news users won't do that because they complain about Apple not because they are close or monopoly, but they make squeezing money from web users a little bit harder
No, Google does not control "the web". You're trying to divert the conversation to Google instead of the topic of Apple's abusive business practices.
Apple doesn't even make Safari for any other platform anymore. They used to but they decided to stop. They could compete with Google's web browser, but they don't. They prefer to stay in their closed ecosystem, not even trying to compete and forcing other browser makers to use their browser engine.
Maybe we should talk about why Apple doesn't make Safari for other platforms and their abusive business tactics, instead of whatever Google does.
Chrome isn't exclusive to one platform, and conversely Android doesn't force you to use it across the entire operating system.
If Chrome is forcing Web standards even in places where no one wants them, the equal and opposite problem is that Safari has a long history of holding back Web standards that are inconvenient to them, and making the entire industry bend around them because their users don't have the option to just install something else.
Part of the problem is actually that Apple also won't really compete here. They want the vertically-integrated everything, and so WebKit everywhere other than their devices is a second class citizen. The support for its underlying stack anywhere else -- from Linux-based browsers like GNOME Web to runtimes like Bun using JavaScriptCore -- has come pretty much entirely from third parties, and there doesn't really seem to be any sort of toolkit analogous to the CEF that could be used to embed it into other applications.
If anything, the only viable effort to make WebKit available across platforms was Chrome.
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
As long as this is the current state of things with WebKit, the counterweight to that is that Apple ultimately gets veto power over any standard the rest of the industry does agree on.
I mean, Web Workers is something only Google could love. They could have provided an API that would let you give commands to the cache layer of the browser and it would have the speed and reliability of native code behind it and if the system wants to evict one piece of data from the cache to deal with storage pressure... it can. Instead they invented a Rube Goldberg machine which doesn't really do anything and you have to write another Rube Goldberg machine inside the first Rube Goldberg to get "offline operation as a service." And you've got to deal with all the async programming difficulties and unreliability and I know for years all the storage operations you could back it with are awful.
Like I'm the guy who signs off on the ticket being done and I've been the guy who answers the pager when it goes off in 2 in the morning and even when I'm getting a stage demo ready for somebody who has the improv acting and stage magic skills to make a 20% done app look like... magic I have to get that 20% functionality working 100% in some certain sense and the Web Workers API screams "you're going to mess around with this forever and it's never really going to work right" where the product is under or over baked.
So the discussion about PWAs is another one of those discussions that SV has with itself without involving the other 99% of software developers and web users. Google might have had a lot more luck pushing it had they involved a focus group of people in Minnesota or Dublin somewhere.
And of course that 1/3-baked notifications API just raises my hackles, like the first thing I am going to do with a new web browser is turn it off. I mean, every web site is already trying to spam me every way it can possibly spam me, the last things I need are another pop-up menu that covers content, another dialogue of any kind to close, and the possibility that I'll click the wrong button and get spammed.
(And in the "iOS sucks" department, notifications are a big part. I've found that if I have any kind of filtering or groupings I lose important notifications, I will find out i got a text message from my son a week after I get it, etc. To have a decent experience I have to turn filtering/grouping off and give notifications permissions to the few apps that I need notifications from)
Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.
They don't trust third parties to keep up with exploits on such a large attack surface.
The sheer quantity of old school Flash's exploits were a recent memory when the policy was set.
> …having equivalent PWA support to Android would drastically impact App Store revenue.
This would be a credible argument if PWAs on Android had any impact.
Safari desktop, however, even lets me wrap web apps like Slack that weren't coded to support PWA.
PWA installation is also more hidden on iOS, it can't be initiated from a user interaction on the page. The user has to manually go through the share menu, a very non-intuitive location.
> This would be a credible argument if PWAs on Android had any impact.
How are you so sure they don't? Regardless there is less necessity on Android. Google Play store rules and fees are slightly more favorable, there's also third party app stores, and side loading.
For others, here's the real truth of the matter: https://infrequently.org/series/browser-choice-must-matter/
> For others, here's the real truth of the matter:
Just look at this person's history and tell me they're objective. I have no skin in the game, other than being a fan of the web as a platform generally and PWAs specfically.
Here's our most recent exchange https://news.ycombinator.com/item?id=49727868
and this org is doing the most and best work to force Apple to change. Please support them: https://open-web-advocacy.org
That sucks, for sure, but I don’t see why that stops the browser vendors. Like… why wouldn’t just release a second app and see how it performs?
So.. Yes. More hoops to jump over, less competition, bigger market share, profit.
Safari has JIT. The webview you use inside apps runs in its own process, and has JIT. If you run JavaScriptCore in your own process, it doesn’t have JIT. So they’re clearly concerned about the possibility of JIT breaking some kind of security concern.
Browsers in iOS is just one of the most infamous examples, but they do it all over the place.
Safari is as bad at PWAs on iOS as Firefox is for PWAs on Android. https://pwascore.com/
I mean, that's the prevailing notion.
There's the question of battery life, but that isn't really well served by having e.g. poor touch sampling when a WebGL app can easily go through the entire battery of an iPhone in an hour.
I purchase native apps whenever I need to. I wouldn't mind purchasing a web app if that was the best option, but where are they for sale?
I wouldn't be surprised if Google will start attaching Firefox even on Android in favor of Chrome... the sole reason they probably didn't already do so is that they fear sanctions from the EU and other countries that have antitrust in place.
You need to be up-to-date if you're going to spew bullshit. Ask the AI first.
If I can't replicate that on iOS then it's not "just fine," imo, and I presume that's the GP's point. If I can't do that, the "bullshit" is the claim that adblocking works on iOS.
> SponsorBlock, how are you running that?
This is literally available in the app store, if you choose not to use Brave / Orion.
SponsorBlock has an officially supported iOS app (or you can use Orion browser)
I had it in my head that that somehow wouldn't be possible without Apple allowing other browser engines. Happy to learn I was wrong!