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

51–60 of 285 posts

Re: What PWA Can Do Today

#51

Post by MBCook »

ajross wrote: post #49
starfox64_ wrote: post #4

It's kinda sad that the website doesn't prominently display which features have "universal" support across iOS and Android. The whole point of PWAs is to provide cross platforms apps so if a feature isn't available on all/most platforms, I don't think it's fair to say that it's really usable at all in your PWA.

Doesn't https://caniuse.com already fill this need? This article is just evangelism, if you want technical sources the community has had you covered for a long time.

Sure you can look things up but it would be nice to look at this evangelism site and tell at a glance that Bluetooth isn’t supported everywhere the way playing a sound is.

Re: What PWA Can Do Today

#52

Post by spiffytech »

SPBS wrote: post #25

Call me back when PWAs can be registered as share targets on iOS (i.e. it appears as an app on the share sheet when you click "share" on a web page). I really want the ability to bookmark sites I browse on my phone and save it to a self-hosted web application.

Web Share Target API isn't a good experience on Android either.

Partly because it only works if the user visits your site with Chrome for Android (even Chromium browsers don't work).

And partly because receiving a share unrecoverably takes over whatever the user is doing. If the user opens something from your PWA (an external link, another app) and then shares back into your PWA, whatever they were looking at gets killed and your PWA navigates to the share target.

I'm building a web app built around sharing and I'm going to have to wrap it in an Android app solely to get around this.

Re: What PWA Can Do Today

#53

Post by MBCook »

hutzlibu wrote: post #32
fidotron wrote: post #22

On a purely technical level the main thing stopping PWA adoption is the JS front end universe being addicted to front end frameworks which destroy the UX of websites and PWAs, but there is a key value add with app stores which PWAs will never have: trust, and much as the Apple haters will hate it it is much stronger on the iOS App Store because of the very things they hate about it. Chrome, for all of Google's sins,…

"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.

Re: What PWA Can Do Today

#54

Post by bodantogat »

fidotron wrote: post #22

On a purely technical level the main thing stopping PWA adoption is the JS front end universe being addicted to front end frameworks which destroy the UX of websites and PWAs, but there is a key value add with app stores which PWAs will never have: trust, and much as the Apple haters will hate it it is much stronger on the iOS App Store because of the very things they hate about it. Chrome, for all of Google's sins,…

On IOS, I can't install a PWA/add to home screen with a simple click. I think thats the bigger obstacle.

Re: What PWA Can Do Today

#55

Post by amadeuspagel »

lolinder wrote: post #42
amadeuspagel wrote: post #40

Earlier quoted context omitted.

If bluetooth is so essential that a substantial portion of the web will rely on it, then maybe other browsers should support it.

You're still focused on the Bluetooth, but that's just one tiny part of a larger pattern of Google ignoring the rest of the vendors and doing what they want. The death of the web, if it occurs, will be death by a thousand cuts.

Bluetooth is the example that you chose, and that I used to make a general point, which also applies to any other API.

Re: What PWA Can Do Today

#56

Post by hotgeart »

pjmlp wrote: post #48
starfox64_ wrote: post #4

It's kinda sad that the website doesn't prominently display which features have "universal" support across iOS and Android. The whole point of PWAs is to provide cross platforms apps so if a feature isn't available on all/most platforms, I don't think it's fair to say that it's really usable at all in your PWA.

PWAs are the next step in mobile Web, for most forms over data apps, it isn't really needed. When I came back to Web/Distributed Systems after my stint dealing with Windows desktop, all the applications I have been involved only had Web frontends, including for mobile devices, not Web views, the actual browser. They managed perfectly fine.

> PWAs are the next step in mobile Web

For subscription app may be, but all ads revenue websites will reject it.

Re: What PWA Can Do Today

#57

Post by DaiPlusPlus »

jwells89 wrote: post #50
fidotron wrote: post #33

Earlier quoted context omitted.

Honestly, I believe you have this backwards; the problem with browsers is they are too flexible and complicated. If you delivered a consistent MVC framework in the style of the classic NeXT APIs the major complaint would be the imposed look and feel, which from the point-of-view of a user is a feature, but for whatever reason people are drawn like moths to a flame towards that which is at the edge of reasonably possi…

It depends on what part of browsers are being spoken about. They’re plenty flexible and capable for the case of traditional pages and server-side apps, but it’s a totally different story for interactive widgets and especially full blown SPA’s. For example, browsers don’t furnish a tableview/datagrid or even a basic single column recycler view, meaning one has to find a third party library to do those things that’s st…

> For example, browsers don’t furnish a tableview/datagrid or even a basic single column recycler view

and ? Or am I missing something?

Re: What PWA Can Do Today

#58

Post by pjmlp »

hotgeart wrote: post #56
pjmlp wrote: post #48

Earlier quoted context omitted.

PWAs are the next step in mobile Web, for most forms over data apps, it isn't really needed. When I came back to Web/Distributed Systems after my stint dealing with Windows desktop, all the applications I have been involved only had Web frontends, including for mobile devices, not Web views, the actual browser. They managed perfectly fine.

> PWAs are the next step in mobile Web For subscription app may be, but all ads revenue websites will reject it.

There are many types of applications out there besides ads.

Re: What PWA Can Do Today

#59

Post by fudged71 »

I see there are a few features not available on my phone (iPhone 15 Pro Max). If possible it would be great if the feature icons could turn grey if they aren’t supported on the current device

Re: What PWA Can Do Today

#60

Post by exabrial »

My estimate is there are 5,000-10,000 really poor PWA/SPA/etc for every actual good PWA/SPA.

Going to a website and it loads some massive chunk of overengineered javascript when all I need to do is display one piece of text is infuriating.

Post reply on HN