Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What PWA Can Do Today

whatpwacando.today

Post reply on HN
Print view View original

211–220 of 285 posts

Re: What PWA Can Do Today

#211

Post by doublerabbit »

hoten wrote: post #205

Why does the HN crowd love to leave comments of mean criticism as if it was certain the creator of the submitted site wasn't going to see it? You can levy critique without being rude. Not many are doing this, but it doesn't take much. Maybe letting harsher-than-necessary criticism wash over you is necessary for putting any creation out into the world, but it still feels bad to see. This is why people outside this com…

The HN crowd are mainly developers who feel that their opinion is strictly correct with no leeway; as per developer culture.

If it's not Apple, Go or Rust; or some ten-story sandwich stack of cobbled together libraries, it's deemed trash. Don't you dare mention Java.

But what do I know, I'm just a sysadmin after-all. Everything is full-cycle cynicism to me; tomorrow we will be bitching about SPA's again and praising some new reinvented library.

Bring back ActiveX and JavaApplets.

I'm sure I'll get some "deemed worthy" downvotes for this comment; and I think I need more tequila.

Re: What PWA Can Do Today

#212

Post by hn_throwaway_99 »

CharlesW wrote: post #120
hn_throwaway_99 wrote: post #81

Earlier quoted context omitted.

> Progressive enhancement, API detection, and polyfilling are all common strategies that can be used to mitigate almost all device differences. Keyword being "almost", and that in some cases if the platform doesn't support your feature, you're shit outta luck. By far the thing that prevented PWAs from bigger uptake earlier was Apple dragging their feet on push notifications support on iOS. There was simply no workaro…

> By far the thing that prevented PWAs from bigger uptake earlier was Apple dragging their feet on push notifications support on iOS. Is there any evidence that this moved the PWA needle at all, he said hopefully? I would've predicted no effect on PWA adoption. > …last I checked the "install to home screen" on iOS Safari was still a horrible user experience (the actions is hidden under the "share" menu, which makes n…

> what would be easier than (1) tap Share, tap (2) Add to Home Screen?

In what universe does "adding to home screen" have anything to do with sharing? It's completely nonsensical.

As others have noted, it would be trivially simple for browser makers to explicitly have something in the address bar or a pop-up that allows users to install.

Re: What PWA Can Do Today

#213

Post by mardifoufs »

hoten wrote: post #205

Why does the HN crowd love to leave comments of mean criticism as if it was certain the creator of the submitted site wasn't going to see it? You can levy critique without being rude. Not many are doing this, but it doesn't take much. Maybe letting harsher-than-necessary criticism wash over you is necessary for putting any creation out into the world, but it still feels bad to see. This is why people outside this com…

Especially for an article about... PWAs. It's so weird to be this worked up about this, like sure maybe they suck but that's not the point of the article. It's like getting mad at someone for writing a c++ article because it's not a memory safe language... like... okay!

Re: What PWA Can Do Today

#214

Post by postalrat »

tgv wrote: post #134
postalrat wrote: post #19

Earlier quoted context omitted.

Apple wants to keep in control with the app store. PWAs threaten that control. So much so apple doesn't allow other browsers.

While Google wants as much access to your phone as it can get. Why would that be?

If its that simple then why is Apple blocking the most useful features like push notifications and add to home screen? Those aren't particularly useful for tracking.

Re: What PWA Can Do Today

#215

Post by postalrat »

JimDabell wrote: post #21
postalrat wrote: post #19

Earlier quoted context omitted.

Apple wants to keep in control with the app store. PWAs threaten that control. So much so apple doesn't allow other browsers.

That argument would work if it were only Apple rejecting them. Mozilla rejects them on the same grounds.

Mozilla rejects stuff like webusb while apple is blocking add to home screen, push notifications, etc. Stuff that is needed to replace many app store apps.

Firefox supports both add to home screen and push notifications.

Re: What PWA Can Do Today

#216

Post by mdhb »

MBCook wrote: post #53
hutzlibu wrote: post #32

Earlier quoted context omitted.

"On a purely technical level the main thing stopping PWA adoption" I rather think, the main thing stopping PWA are that browsers still can not decide how to treat them. In some ways you can just do anything unrestricted and in other areas your PWA gets treated and limited like a random untrusted website, with no way to get needed rights. At least that was my experience last time I messed with it. It is of course a pr…

Go to any webpage/PWA, hit the share button, hit “add to home screen“. That’s it. It’s not complicated or restricted in any way.

Absolutely nobody expects to find installation options under layers of indirection in a share menu.

It’s an intentional choice by Apple that’s hostile to users but very aligned with their strategy to lock users into their own proprietary platform as much as possible.

Re: What PWA Can Do Today

#217

Post by mdhb »

wg0 wrote: post #187

Just wondering why mobile platform gate keepers, even Google would allow PWAs which will erode the value of their platform.

Because holding customers hostage is a shit strategy?

That and the fact that there is a large legal aspect to all of this largely led by the EU that seeks to prevent that kind of anticompetitive behaviour.

Re: What PWA Can Do Today

#218

Post by doublerabbit »

mvkel wrote: post #103

As soon as I tapped into this site, the browser's back button got hijacked and half of the features don't work. This is why (imo) PWAs should not try to replicate native app functionality, but instead recognize the web for what it is and play to its strengths.

> As soon as I tapped into this site, the browser's back button got hijacked and half of the features don't work.

Sounds like common SPA application features to me.

Re: What PWA Can Do Today

#219

Post by mvdtnz »

matt-tingen wrote: post #185
mvdtnz wrote: post #131

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.

Unfortunately, feature detection indicates that Firefox on Android supports vibration, but it doesn't currently work. https://bugzilla.mozilla.org/show_bug.cgi?id=1653318

Par for the course on Firefox I'm afraid. Every time I give it a chance it lets me down.

Re: What PWA Can Do Today

#220

Post by baranul »

doublerabbit wrote: post #211
hoten wrote: post #205

Why does the HN crowd love to leave comments of mean criticism as if it was certain the creator of the submitted site wasn't going to see it? You can levy critique without being rude. Not many are doing this, but it doesn't take much. Maybe letting harsher-than-necessary criticism wash over you is necessary for putting any creation out into the world, but it still feels bad to see. This is why people outside this com…

The HN crowd are mainly developers who feel that their opinion is strictly correct with no leeway; as per developer culture. If it's not Apple, Go or Rust; or some ten-story sandwich stack of cobbled together libraries, it's deemed trash. Don't you dare mention Java. But what do I know, I'm just a sysadmin after-all. Everything is full-cycle cynicism to me; tomorrow we will be bitching about SPA's again and praising…

[dead]
Post reply on HN