Apps have millions of different end-users.
I’m reading a slight bristling of superior attitude coming from responses to Ben’s post.
My Clients get what they ask for. If they ask for a PWA I’ll build it no issues, but as of yet… Nope, nada, zilch, no interest.
Is it possible that these “uninterested” clients are offered One Nail solutions as vastly preferable from the get-go?
Seeing as how the developer is convinced they are the only mobile app solution that smart people should choose?
Unfortunate.
Wouldn’t still be in this business if that were the case.
What RELEVANCE do your PERSONAL daily preferences have to do with it?
Is this how you belittle clients?
Read my above posts before trying to bate me in to wasting time on the assumptions you make above. Everything is explained.
Well…his personal daily preferences are based on his professional experience which is pretty extensive and deep if you ask me. The guy knows his stuff.
I like PWAs. Specially the part where I don’t depend on Google and Apple but that doesn’t mean he is not right.
Can PWAs offer push notifications? That seems to be the biggest difference between PWA and native app. But with sockets and nodejs, I’m wondering if that now solves it?
Thank you @JonL that is very kind of you indeed. I can also be a bit of a dickhead so sometimes what I type may come across in the wrong way. I confess to learning a ton from @ben and in no way measure manhoods nor wish to insight any type of measuring contest with anyone. Am here to learn and make friends. I’m also not here to piss on peoples bomb-fires. Please feel free to take what you wish from this response. And when it does come time to put a PWA together guess who the first person will be I ask advice from…!?! @ben most definitely. So as well as not pissing on bomb-fires I ain’t here to burn bridges either!
Of course you are a dickhead. Aren’t we all? 
But people tend to confuse opinions and facts. Not everything is a fact, but not everything is an opinion either.
Please have a look at:
This is an excellent video, @ben. Thanks for sharing.
It would be great if Wappler could add these actions.
Since this forum category, Coffee Lounge, is more informal in content and allows free flows of yeas and nays I post these links.
Users of Wappler come from different backgrounds with different experiences. Many are NOT very experienced with Phone App development and haven’t come across the current discussions on other forums about the changing “standards” at the Apple IOS Store that could impact future development decisions for Developers.
So, to broaden the discussion of Native Apps vs. PWAs or PWS — 
For the sake of information, an article from June 2020
Issues with the Apple Native App Store that could impact decisions on whether developing a Native App for IPhones is the first choice or whether developing a PWS might be a better longterm strategy.
Other developers have started speaking out using the hashtag AppStoreAntitrust on Twitter, telling how their apps were refused, and some have even expressed dismay at having to give up on apps they were developing, or not even try to develop certain apps, because of the uncertainty of whether they’d be approved. One example is this Twitter thread from the long-time Mac app developer Rogue Amoeba, telling how they had apps refused, and eventually gave up selling on the iOS App Store, and, with the exception of one app, on the Mac App Store as well.
https://www.intego.com/mac-security-blog/the-pros-and-cons-of-apples-ios-app-store/
Additionally, here’s another article from an experienced App developer who knows the ins & outs of the Apple App Store environment. Increasingly, the risk with an Apple Native App is essentially “What Hidden Rules will be changed or added tomorrow or next week that will kick my IOS App out of the store?”
One of his claims in this link:
. . most mobile apps, especially on iOS, are not a good channel to promote and engage your customers. App installs are rare for most apps. Development, maintenance and marketing for these apps is also very expensive.
PWAs are very interesting and relevant nowadays indeed. Many users complain about having to download native apps. They want their phone’s storage used up by photos, not apps that, cheery on the cake, may steal their private information.
But Ben (and Wappler team), we need easier (no-code?) steps for turning a website into PWA. Current tutorials are too complicated for newbies like me.
I came across this article from October, 2020
It reveals that Microsoft is PUSHING PWA’s for accessing their own Office cloud services.
The main development hurdle for them AT THIS MOMENT is that the vaunted “work offline” advantage of a PWA is not available for Office services if your device is not online. But, they ARE Microsoft & I assume they are already working on this.
Our most recent Project is now a PWA (took about ten minutes to conform to PWA requirements). Mobile, Web, and now PWA from a single Project source (all thanks to Wappler).
Actually all the new streaming games services like Nvidia gforce now and google stadia are all PWAs as Apple won’t allow then in App Store.
And they run streaming games in the browser! Who would ever thought that would be possible
We’ll go back to PWAs… Need to figure out the caching issues first though. No good for Security Provider and with users switching to lots of other users accounts within a PWA the cache never clears unless an update is pushed? Not a big problem. Seem to be plenty of options to work around this, but no rush! Just not right now.
Some Western world web app developers apparently haven’t travelled enough to understand that their own speedy internet services connections are far superior to those in the majority of nations.
Resources loaded by websites & mobile apps must be as lightweight as possible. It is not old-fashioned to look at image, js, css files, even CDN loading and consider where to prune components for the sake of the most essential usability online.
Excerpt from the linked article:
All those lessons we learned optimizing web pages for dial-up became super-useful again when mobile took off, and they continue to be applicable in the work we do for a global audience today. Unreliable or high latency network connections are still the norm in many parts of the world, reminding us that it’s never safe to assume a technical baseline lifts evenly or in sync with its corresponding cutting edge.
https://alistapart.com/article/request-with-intent-caching-strategies-in-the-age-of-pwas/
Good example of MAJOR companies who can not qualify for inclusion in the Apple App store.
I understand the necessity of having a “safe” App source that the user can trust. But Apple’s record so far is that too many Apps cleared by Apple were NOT Safe and even predatory in transmitting highly sensitive data to third/fourth party bad actors.
And Apple has been, with evidence, accused of simply prioritizing app approval based on whether given app will sell Apple devices or online services.
Maybe the best option is make a PWA and put it in a Webview(Framework 7, Flutter, React). And maybe add a onboard screen and something else like this stores think they are native.
For me the problem with the PWA is how you put it in your home screen. Should be some option to put on the screen instead of the first notification.
I am the type of person that I prefer web apps than native apps.
