Regarding PWA support, I often read you can use PWAs offline. I can not imagine a Website that I would want offline. Can someone please give me an useful example of such an offline Website?
For developers, Safari is crap and outdated
101–110 of 623 posts
Re: For developers, Safari is crap and outdated
#102Earlier quoted context omitted.
Actually, pretty sure it's only one reason, money. If they made Safari on iOS actually good (re: PWA notification support), it would burn into their App store profits.
Safari is still the best mobile web browser in terms of performance and usability, and I'm using Firefox on Android, it's great, but Safari is the fastest.
Considering there are no other browsers on iOS to compare to, Safari is obviously the fastest by default.
Re: For developers, Safari is crap and outdated
#103People complain about Google Chrome eating the web, but it really does seem like everyone else either dislikes the web (Apple), is ambivalent (Microsoft), or plain doesn't seem to care much (Mozilla).
Follow the money. Apple makes its money from iOS & the apps ecosystem. Microsoft from business licenses. Mozilla – well they try their best but don't make much money at all. The only company to successfully monetize the open web is Google. Facebook as well to an extent but they found their success in mobile more than web, so gave up caring too much.
The majority of Mozilla’s operating funds come from Google.
Re: For developers, Safari is crap and outdated
#104I speak as a non-developer but as someone who makes their living with a computer: From my perspective, Apple's conservative attitude is a positive. There are all sorts of web techs that enable the possibility of increased tracking, of websites being generally malicious, of all sorts of things that I don't want. Historically Apple has been on my side and I will continue to appreciate that until demonstrated otherwise.
Are you implying Mozilla Firefox cares less about the user than Apple? Why not let Mozilla have it's browser on iOS? It's not about the user, it's about having an iron chokehold on the developers and we are too cool aid drunk to call it out.
Mozilla is mostly funded by Google.
Re: For developers, Safari is crap and outdated
#105https://www.theregister.com/2021/06/16/apple_safari_indexedd... this bug is still not fixed, which is kind of nuts. Well, they said they fixed it in dev but have not actually deployed the fix yet and won't comment on when that might happen.
Was this not fixed in the release a few days ago?
Re: For developers, Safari is crap and outdated
#106Earlier quoted context omitted.
Thank you. I have no idea what these people are talking about. They obviously didn't actually do development back then. > Apple took years to finally add WebRTC support to Safari, far enough behind Chrome and Firefox that it practically became a running joke among developers and even industry observers. Really? Because no one I know uses WebRTC and would rather use ffmpeg and sockets to do serious work like that over…
Lots of sites use WebRTC for video and audio calls. Google Meet, Discord, Slack for example. On desktop it's far more secure to use those in-browser than via desktop apps.
Yeah, and those all suck up my RAM. Color me nonplussed that WebKit doesn't follow in Chromium's footsteps.
Re: For developers, Safari is crap and outdated
#107Earlier quoted context omitted.
> Reddit is a pretty low bar Reddit is a multi billion dollar product and one of the most trafficked sites on the internet.
If you've ever used their mobile site, it's clear they go out of their way to sabotage the experience so that people will use the native app instead
Shit they even admit as much with the popup for the app saying "it's better in the app".
Re: For developers, Safari is crap and outdated
#108Earlier quoted context omitted.
Actually, pretty sure it's only one reason, money. If they made Safari on iOS actually good (re: PWA notification support), it would burn into their App store profits.
What sort of apps are in the intersection of being performant enough to be written in JavaScript and also generate lots of in-app purchase revenue (which is typically recurring revenue)? Certainly not most games, which are the biggest money-spinners, and also not pro camera apps or video editing apps. Video streaming apps (eg. Netflix / YouTube Premium) come to mind, but they don't rely too much on in app purchase I…
> What sort of apps are in the intersection of being performant enough to be written in JavaScript and also generate lots of in-app purchase revenue (which is typically recurring revenue)?
Or maybe it's just selection bias - we don't see these types of apps because the experience is so fundamentally broken, noone ever bothers to develop them.
Re: For developers, Safari is crap and outdated
#109Earlier quoted context omitted.
It’s more often than twice a year, at that. It would be nice if Safari and Safari WebView were updated more frequently like Chrome and other browsers, but the pace that exists is not as slow as people like to pretend.
OS updates happen more often, but Safari’s browser engine (WebKit) gets updated with bug fixes and new features exactly twice per year (in March and September), AFAIK.
New features typically land in March and September, because they are often supported by the underlying OS.
For instance, HTTP/3 support should land in iOS 15 and macOS 12 because it is being added to the operating system frameworks.
Bug fixes can arrive even in maintenance releases, but this is more often seen for security-related fixed (such as remote exploits or side channel attacks)
Safari itself is shipped outside of the read-only container on macOS so that it can be updated independently.
Re: For developers, Safari is crap and outdated
#110Earlier quoted context omitted.
Lots of sites use WebRTC for video and audio calls. Google Meet, Discord, Slack for example. On desktop it's far more secure to use those in-browser than via desktop apps.
Yeah, and those all suck up my RAM. Color me nonplussed that WebKit doesn't follow in Chromium's footsteps.
I don't see how that's an argument for not supporting WebRTC...