151–160 of 198 posts
Earlier quoted context omitted.
> Native File System API Great, so there is light at the end of the tunnel! > store that data on the server Well, we talked about that already: https://news.ycombinator.com/item?id=23793541
I wonder how Mozilla will handle this, given that so far they deemed file system access as too dangerous even for extensions, nevermind random web pages…
Earlier quoted context omitted.
Not many websites explicitly require Chrome. I don't know what you mean by 'My iOS device has never once shown me "this website requires Chrome."' Why would your iOS device ever need to show such a message, unless it's implemented by the website itself? I don't understand the scenario you're describing at all.
You missed their point. Apple only allows the Safari browser engine to run on their phone. So Google (and other web developers) can't do what they do on other platforms which is only test their website on Chrome or block users of other browsers. For example, Firefox on Android gets a crap Google search from like 2005 unless you spoof your user agent and it works perfectly. By that mandate has kept complete control ov…
If a website doesn't work in Safari, it just doesn't work. That's it. I do know that devs have to work A LOT harder to get things to work in Safari when compared to Chrome or Firefox. It's like Safari is the new Internet explorer.
Earlier quoted context omitted.
Apple is making the right decision here. My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why. Maybe some day, web apps will become so undeniably awesome that Safari's position is untenable. But the agitation is not coming from iOS users missing out on awesome PWAs. Instead it's web developers, who are just annoyed t…
I couldn’t agree more. As a developer, PWAs are amazing. Write once, run more or less everywhere. Our enterprise software deployments wouldn’t have been possible if we had to target iOS, Android and Windows specifically. As an end user, I dread the days PWAs ever go mainstream. They’re horribly inefficient from a power and performance point of view, and never have I come across a PWA with a user experience half as go…
If TikTok was a PWA it couldn't have done a fraction of the tracking it was doing. The irony is that apple is forcing you to use a much more privacy-invasive alternative to PWAs.
Earlier quoted context omitted.
I agree. Apple is stifling innovation by not supporting certain APIs. They need to stop doing this, or they will hurt themselves in the long run. As it is, most people use Safari on iOS because they are forced to - all other browsers on iOS are forced to use WKWebView, which basically means they are wrappers around Safari's view. To this day, I can't understand why their users stand for this. In this regard, Apple re…
Apple is making the right decision here. My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why. Maybe some day, web apps will become so undeniably awesome that Safari's position is untenable. But the agitation is not coming from iOS users missing out on awesome PWAs. Instead it's web developers, who are just annoyed t…
Do you mean UI conventions, or the "30% revenue cut and a gag order on even mentioning non-appstore signups" convention?
Justifying blatant anticompetitive and user-hostile practices by native UI holyness is getting kinda old.
PWA = Progressive Web Apps A progressive web application is a type of application software delivered through the web, built using common web technologies including HTML, CSS and JavaScript.
Hey! I see a lot of confusions on PWA on what they can or can't do in the comments. I've written an article trying to address that in a fun way: https://www.davrous.com/2019/10/18/myth-busting-pwas-the-new... by busting 9 common myths on Progressive Web Apps. For instance, they can use WASM which is production ready for years in all browsers!
* is installed
* may run offline
* may use extra system resources
Earlier quoted context omitted.
Apple is making the right decision here. My iOS device has never once shown me "this website requires Chrome." I get to use the mobile web without needing Google. And Apple is the only reason why. Maybe some day, web apps will become so undeniably awesome that Safari's position is untenable. But the agitation is not coming from iOS users missing out on awesome PWAs. Instead it's web developers, who are just annoyed t…
I couldn’t agree more. As a developer, PWAs are amazing. Write once, run more or less everywhere. Our enterprise software deployments wouldn’t have been possible if we had to target iOS, Android and Windows specifically. As an end user, I dread the days PWAs ever go mainstream. They’re horribly inefficient from a power and performance point of view, and never have I come across a PWA with a user experience half as go…
Many didn’t understand what a web app was until recently and now they want nothing else. For starters the speed and ease of deployment can also impact the user experience; people love seeing problems fixed and tweaks made on the fly in reaction to their feedback.
But more than anything they’re thoroughly impressed with the interfaces compared to other shitty desktop enterprise software they use. At the end of the day it’s the same story as with all software: quality often depends more on craftmanship than on the flavor of tool that you’re using. PWAs offer enough means to build beautiful and performant software, with full offline capabilities that can make them nearly indistinguishable from a native app.
I can’t disagree that native apps have advantages in some use cases. For the most part I wouldn’t build something like a graphics editing program as a web app - companies like Figma challenge this, but they’re using techniques at the edge of web dev that go beyond PWA capabilities (eg, WebAssembly), and unless you have an all-encompassing product strategy like they do you’d probably be better off building something like that native.
For many CRUD app use cases however PWAs can be more than sufficient. I’m very bullish about their future, and I wouldn’t be if I hadn’t seen real, happy users, because that's what matters to me the most.
PWA = Progressive Web Apps A progressive web application is a type of application software delivered through the web, built using common web technologies including HTML, CSS and JavaScript.
So it’s a new name for a website?
- Fast (cache with service worker)
- Reponsive (no explanation needed)
- Offline page (so if the user lost connection or the web site is cached and he visite when he's no connection the app should work or at least display a custom offline page)
- Engaging (fancy word, to say it's need to behave like an app + push notifications)
- Installable (if the browser is compatible and you visite the website more than once it'll ask you if you want to install the app. This will create a shortcut and when you click on it it'll open like an app (no address bar))
But Apple is very late and don't support all of this.