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

181–190 of 285 posts

Re: What PWA Can Do Today

#181

Post by alternatex »

Longhanks wrote: post #141
onion2k wrote: post #67

Earlier quoted context omitted.

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. You should be delivering the best possible experience for the user based on what their device can do, not the lowest common denominator of some arbitrary set of features. Progressive enhancement, API detection, and polyfilling are…

> You should be delivering the best possible experience for the user based on what their device can do, not the lowest common denominator of some arbitrary set of features. So the exact opposite of PWAs.

Technically that's what Progressive means in Progressive Web Apps. That the developer enables features for customers based on the browser API support on their device, inadvertently ending up with software that works differently on every person's device. You might not like it, but that's what peak Chromebook performance looks like.

Re: What PWA Can Do Today

#182

Post by asabla »

oaiey wrote: post #161
bob1029 wrote: post #38

We push PWAs to iPads & Surface Go devices via Microsoft InTune for some of our clients today. This path started out very nightmarish (circa 2020) but it's going much smoother today. One of our customers actually came back to us with a slightly improved process based upon the one we gave them. They switched from iPad to Surface Go and used some extra endpoint management to make the PWA experience into a sort of kiosk…

As a Microsoft shop: Any experience with Blazor and PWA? I find Blazor very awesome for developing an App using WebAssembly. When using it as a PWA and caching the .NET runtime locally etc, the combination of productivity and ease of deployment could be theoretically really awesome.

Built an application using strictly Blazor wasm for my last assignment (so .Net 7).

It wasn't a easy ride (especially when it comes to LSP support for razor pages). But the overall experience was pretty decent.

Almost half of our users preferred to use the application as a PWA (using windows 10 and edge) instead of an ordinary tab in your browser.

Somethings to consider tho: Upgrades to service workers and what not can be a bit challenging depending on your situation.

Keep in mind that a lot of firewalls and antivituses may block all those binary downloads (since it's just dll files). There are ways around it ofc, but still expect files to be blocked.

Authorization changed between .net 7 and 8. So make sure you understand what these changes are (if you use packages from Microsoft)

Re: What PWA Can Do Today

#183

Post by alternatex »

JumpCrisscross wrote: post #123
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 For me, it was developers trying to push Android design language via PWAs. In others, it was what should have been a website being packaged as a PWA, which is just clunky. That combination made PWAs feel cheap compared to native apps or sites.

PWAs are cheap compared to native apps. That's the whole point.

Re: What PWA Can Do Today

#184

Post by alternatex »

moffkalast wrote: post #83
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.

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

Re: What PWA Can Do Today

#185

Post by matt-tingen »

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

Re: What PWA Can Do Today

#186

Post by bob1029 »

oaiey wrote: post #161
bob1029 wrote: post #38

We push PWAs to iPads & Surface Go devices via Microsoft InTune for some of our clients today. This path started out very nightmarish (circa 2020) but it's going much smoother today. One of our customers actually came back to us with a slightly improved process based upon the one we gave them. They switched from iPad to Surface Go and used some extra endpoint management to make the PWA experience into a sort of kiosk…

As a Microsoft shop: Any experience with Blazor and PWA? I find Blazor very awesome for developing an App using WebAssembly. When using it as a PWA and caching the .NET runtime locally etc, the combination of productivity and ease of deployment could be theoretically really awesome.

Yes. Tons with server-side Blazor apps. We currently use Blazor for our internal admin UIs, but at this point I'd never put it in something customer facing (even in B2B setting).

We haven't played with the client-side WASM stuff, but the conclusion is that server-side blazor is not a fantastic technology if you want something that "just works". Websockets in particular are kind of nasty when you have a client device ecosystem where screens and apps are frequently changing activity state. Stateless forms are much easier to reason about. iOS/Safari is very aggressive with closing down unused resources. Stateless forms can survive for days on those user agents. Our blazor apps would require refreshes after a few minutes of inactivity.

Vanilla web forms & SSR is what we run with today. Our "framework" is to use string verbatim & interpolation operators in C# to compose our responses. Looks something like PHP and has zero dependencies.

Re: What PWA Can Do Today

#188

Post by magicseth »

We built hellowonder.ai as a PWA first, and it was almost amazing! But we use voice input, and ios would pop up the microphone permission repeatedly after a few minutes, even if it had been approved recently. I couldn't figure out how to keep the microphone permission!

So frustrating to be soooo close, and then need to build an iOS app.

Re: What PWA Can Do Today

#190

Post by deathanatos »

Is this satire? I'm not sure what about this is supposed to be a convincing argument for PWA?

Even the text seems wrong? The prose seems to indicate it is installable even outside of mobile … but I have no idea. I'd've expected one of those popup "this site wants…" boxes, but nope?

I also sort of thought PWAs were supposed to be responsive in their UI, adjusting to more/less real estate, but this is just the same UI at any size?

Post reply on HN