I built a progressive web app and published it in three app stores

Re:I built a progressive web app and published it in three a... by zghst on Monday April 16, 2018 @02:33PM (#16851509)

Really this is all about your aversion to paying the fee and to learning how to develop for the respective platforms. JavaScript does not offer performance or optimization near the same levels of native code, etc. On top of that, there are guidelines, accessibility features, and carefully crafted UI components for a respective OS (that have thousands of hours of user research).

The amount of standard APIs developed in JS are nowhere near native APIs, also JS has barely gotten to the point of good enough for native development, whereas, mobile platforms have had 10 years of mature development.

It's quite the fantasy to pretend that PWAs can offer the user anything better than a native experience at this point.

[ Parent | on HN ]

Re:I built a progressive web app and published it in three a... by judah on Monday April 16, 2018 @02:52PM (#16851666)

No, I wrote the post to document how an existing web app can be moved into the app store, the reasons for that, and the hurdles in doing so.

APIs: Yes, Google is improving the situation -- making more and more common OS APIs exposed to standard web interfaces. Meanwhile, Cordova is letting web devs access native functionality that the platform vendors don't expose. The story isn't perfect, but it's actually quite impressive even now.

Web apps: they offer all kinds of things native apps can't. Native apps require install. Native apps must go through approval process for every update. Native apps are restricted in what they can publish on the app store. Native apps are subject to the censorial whims of a single corporation (or government forcing that single corporation). Native apps only work on a single platform; the web works everywhere.

There are lots of wins for web apps. And I think PWAs only increase those wins.

[ Parent | on HN ]