Reply to post: Re: "see the capability gap between native and web apps closed as much as possible"

Google changes course, proposes proprietary in-app purchase API as web standard

Andrew Hodgkinson

Re: "see the capability gap between native and web apps closed as much as possible"

PWAs don't have any less security that a standard web page run through chrome.

YES. Exactly the point.

Reading every update note for every app to see what amazing new features it had. Doesn't happen anymore

Because thanks it large part to agile and in part to lazy change log writing, "nothing apparently changed" updates on a 2 or 3 week cycle with update notes saying something lame like "bug fixes and performance improvements" are the norm. That aspect of lazy development is only tangentially related at best to PWA vs native. People don't read them anymore because app updates are very annoyingly frequent and very rarely have anything interesting to say in the notes.

As for PWA vs Native it's often a different use case and a decent PWA doesn't have to be 'janky and slow'.

Compared to native, sorry, yes it does; the basic domain of HTML, CSS and JavaScript is simply a very poor and very inefficient toolset for constructing the kind of dynamic user interfaces we associate with apps, for which native APIs like Cocoa Touch are dramatically better optimised and designed.

People don't search for apps randomly, it is based on a real user need and most people would prefer not to download a full blown native app just to get information when staying at a hotel, or pay for their pizza etc.

So your argument here appears to be that a PWA is used when people don't want a "full blown app". This is surely a tacit admission of the limitations of the web based environment compared to native. Basically we're saying we just need web sites optimised for mobile a lot of the time. Agree! We don't need or want really to install things. Agree! So, um, wait. What's PWA for again? It's not to replace native apps, and it's a kind of installable thing...

...glorified home screen bookmark with an over complicated cacheing model that would've been better served just by the built-in web browser providing a first class ability to pin things to the home screen? Oh, wait, we have the latter. So, uuuh... All we've really got left is the ability to work offline. And of course, given that we recognise native is best unless you'd really want just to access what's on a web page, and the point of the web page is to be online, we're left with what? Crap games written in JavaScript that'll just about work offline because you jumped through the hoops needed to declare the resource collection in a manner that allows it to be accessed as a PWA?

If it's worth an app, treat your users with respect and make a decent native app that conforms to all your target operating system's best-practice recommendations, layouts, integrations with the rest of the system, accessibility features, and so-on. Have it lean on native frameworks as much as it possibly can to keep the app as small as possible and allow it to conform, often with little or no effort, with things like dark modes or system-wide contrast variations or animation styles or whatever.

If it's not worth an app, just make sure your inherently online web site is a best-possible online web experience on mobile and stop wasting your development money on PWA bundling.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

SUBSCRIBE TO OUR WEEKLY TECH NEWSLETTER

Biting the hand that feeds IT © 1998–2021