Why a Progressive Web App is called..
-
Because a properly written PWA will offer varying service levels depending on which service endpoints it can communicate with. So, an app with no network can still do something. If that app that wants an enclave but only has public internet, it will still have more capabilities than when completely disconnected, while that same app within the enclave will be fully functional.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
For those that want some more information: https://www.slant.co/topics/12815/~pwa-framework[^]
-
Because a properly written PWA will offer varying service levels depending on which service endpoints it can communicate with. So, an app with no network can still do something. If that app that wants an enclave but only has public internet, it will still have more capabilities than when completely disconnected, while that same app within the enclave will be fully functional.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
So in other words, Progressive Web App is a term that describes some software that has (or at least should have been) properly written? 8)
-
So in other words, Progressive Web App is a term that describes some software that has (or at least should have been) properly written? 8)
Not by the classic definition of a web application. The general expectation is that when you navigate to a URL and don't have an internet connection, you won't have a useful web application. If you have PWA contents cached, you will still have an application that can be used. It's a pretty fundamental difference.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
-
This is a question I asked myself recently when a client requested this new fangled PWA nonsense :doh: . What does it actually mean, and why would you want it. Turns out, it's actually pretty cool :omg: and let's you do all kinds of stuff like support your webapp working while it's offline or in bad network reception, push messaging, camera and location access, etc. Of course, these technologies are not called PWA, but they fall under the PWA umbrella, ie, Progressively support advanced features without requiring them for your app to work. Where the term then comes from is you write a web app, and then add stuff like offline caching, location awareness, media access in such a way that the app works to some degree at least even if the browser it's viewed from doesn't support those features. Check out Google's work on this for some excellent examples and explanation (with a top notch framework to boot) Google Workbox
-
I smell marketing, and it makes me want to see if I stepped in dog poop.... fixed that for me, maybe there is some merit to that...
Charlie Gilley <italic>Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Not by the classic definition of a web application. The general expectation is that when you navigate to a URL and don't have an internet connection, you won't have a useful web application. If you have PWA contents cached, you will still have an application that can be used. It's a pretty fundamental difference.
"Never attribute to malice that which can be explained by stupidity." - Hanlon's Razor
It was a 'tongue-in-cheek' comment... Having said that, there are plenty of simple web pages that will not function off-line (ie if you have them in your browser already, they stop being scrollable or even viewable if the connection is dropped), let alone web apps that can cope with the internet connection being dropped during use. Some years ago now I was producing responsive web-apps that worked even when off-line, with data being uploaded to the host when the connection came back etc, so - as always a label has been attached to something that's been around for a while to make it seem new and exciting... 'Cloud' services anyone? I remember the first MS attempt at this. Indeed such things were already in their formative stages whem I was at Uni in the 70s, but of course called something else... :)
-
every idiot (aka Sales/Marketing) is gonna jump on it could have called it a "Web 2.x App" - same effect, hell "Mountain Oyster" would have been even better - everybody likes oysters don't they? OTOH-OT winduds 10 will be 2 years old in April and people are still using it! So old!! c'mon ms, you sleeping on the job? We've had 2 new Androids since wins last version.
I actually like Windows 10. I have to say I truly dislike having to learn "New" version (insert OS/Language/frameworks here). None are necessarily better and they are all full of bugs when they first come out. They are just different. I guess I have a higher tolerance for repetition than you do... :sigh: :laugh:
Late adopters rule.....
-
It progressively takes over your browser.
-
The idea seems good, but I find webassembly a better approach. No JavaScript required, use HTML with C, C++, Rust, Go, C#, Java, Kotlin, Python, or Ruby. Client side or server side. It runs compiled in the browser, with all the same security limits. My experience with webassembly has been with Microsoft Blazor and C#, but I have been pleased with it. Works in every browser the same (so far), except - ironically - IE. Even MS knows IE is dead.
-
This is a question I asked myself recently when a client requested this new fangled PWA nonsense :doh: . What does it actually mean, and why would you want it. Turns out, it's actually pretty cool :omg: and let's you do all kinds of stuff like support your webapp working while it's offline or in bad network reception, push messaging, camera and location access, etc. Of course, these technologies are not called PWA, but they fall under the PWA umbrella, ie, Progressively support advanced features without requiring them for your app to work. Where the term then comes from is you write a web app, and then add stuff like offline caching, location awareness, media access in such a way that the app works to some degree at least even if the browser it's viewed from doesn't support those features. Check out Google's work on this for some excellent examples and explanation (with a top notch framework to boot) Google Workbox