201–210 of 285 posts
Earlier quoted context omitted.
> So many simple setup apps wouldn't need to be native. If they are simple, why not making them native?
Because in native even simple is complicated?
Earlier quoted context omitted.
> or not knowingly That's a big difference. What if I sold you a Linux computer that was actually running Windows with a UI that looks like Linux?
It feels like too complex an example that would need to be constrained in various ways to make it apply. Simpler example: if you've used an Electron app e.g. VSCode, you've used Chrome under the hood.
I use the JetBrains IDEs, made for the JVM.
Earlier quoted context omitted.
Are you using Windows? I am happy that the people who contributed Linux/BSD/Android/iOS did not have your mentality, otherwise I would be forced to use Windows everywhere.
I'm on Fedora. Of course, there has to be a native UI, but I'm running a two-person company for example. How on earth are we supposed to manage three or more platforms (browser, Android, iOS)? We're not lazy but limited by our mortality. > Because they don't know anything other than webtech and don't want to learn?
Are you sure you need three or more platforms? In my experience, when I ask small companies what they need, they say "everything". If I listen to them, they even need to run on a Gameboy. Then most startups fail, so apparently the problem was not the number of platforms.
It feels like many times, selecting the platforms may be fine.
PWAs to me sound like "we want everyone to use the same OS (in this case something like ChromeOS), because that's more productive for us". I get that Google pushes for PWAs because that's how they conquer the OS world. But why do individuals push for that? Because they don't know anything other than webtech and don't want to learn? Have a look at Kotlin and Swift guys, it's kinda cool!
"Cool" is not a great reason. Only having to develop something once that serves all users is great, though. Personally, I cannot stand apps, I only use them when absolutely required, using a PWA gets you all the security of the browser (relatively speaking, but it's a lot more secure than a from scratch black box, and look at goon moves like Facebook embedding a browser that retains third party site interactions) and…
Cross-platform usually sucks in some way. If the app is not worse, the development is: "write once, debug everywhere".
Web is solving that by forcing everybody to use the same (Google-controlled) renderer, so that there is no need for cross-platform anymore: just use the Google thing. I don't want that.
This is why people outside this community often dislike their work being shared here, or at least refuse to read the comments.
Sure would be nice if Firefox desktop would join the browsers that support PWAs. We build an app that has been PWA-first, but it is unfortunate that this generally requires users to have a Chrome instance running. Would much rather point people to Firefox, and it seems like it would be to their advantage to give apps a reason to recommend FF, if they built a smoother PWA integration than Chrome.
Earlier quoted context omitted.
>laws? Maybe. I am not impressed so far, though. >Or force everyone into ChromeOS once and for all. I don't see that happening on iOS.
Still you count on the law to force iOS to accept PWAs, right? Isn't that a bit hypocritical?
I tried two of the features at random (face detection and vibration). Face detection told me my device wasn't supported, and vibration just straight up didn't work. Then I tried to back out of the website and it wouldn't let me. I'm on Android Firefox.
Many advocates will tell you the thing is just as good, or at least more than good enough, and will deliberately avoid telling you about the many pitfalls and not-so-edge cases that they are very much aware of.
Earlier quoted context omitted.
Android allows the site to prompt the user to add it to their home screen, which it can do at a time when it makes sense. e.g. the user orders something, then the "add to home screen" pop-up appears and the user can accept with one tap, which they're likely to want to do because they anticipate wanting to check their order status.
Sadly this is caught up in the usual conflict of interests. As someone building a PWA I would love a quick and easy method to pop up an install dialogue for the user. Unfortunately as a user of Safari on iOS the last thing I want is for every single website I interact with to be popping install dialogues, and you just know that's going to be as prolific as the current bombardment of requests to subscribe to mailing l…
Earlier quoted context omitted.
> "universal" support Apple laughs at your universal support.
Apple spent a huge amount of time and money getting Safari in line with PWA standards in the past few years. Your comment would make sense 3 years ago when it was completely unclear whether Apple will flinch.
They have tried to hobble the web as a platform for fairly obvious reasons for as long as they could.
They don’t deserve any credit for whatever progress they made, it was done unwillingly at gunpoint.