Build once and deploy on every platform and everywhere, we have it before haven’t before?
Discussion now moves to a new web application. This application is defined as progressive web app.
So what is PWA?
The background of this application, is that the application will function for every platform, for every user on every browser.
“By taking the best functionality of native apps (those designed for a specific operating system that leverages device functionality to increase speed and performance) and enabling access via a browser and a URL, PWAs can solve real business challenges,” said Will Morris, managing partner of specialist web design company Achemy Digital.
MobiLens an online company reported in September 2016, on an average every UK Citizen installs zero apps every month. There are currently more than two million apps on the App Store and Google Play, so finding apps will be even more difficult for the users.
The re-engagability factor
Further PWAs should be able to work offline and PWAs should be re-engageable that is it should work when users go away from the app and come back to the app without having to reload the app.
“The increased speed to market competitive edge and low cost of PWAs in comparison to regular apps come hand in hand with their low CapEx and OpEx. Businesses can get their apps to market much faster because they are not awaiting approval from store platforms and can be made available instantly. This also goes for continuous delivery of maintenance updates: no application store approval periods and no need for the user to wait to get their hands on the app, since PWAs are installed on the device y simply adding it to the home page,” said Morris.
Kevin Ferrugia of the Smashing Magazine explains the need for progressive web apps as they take advantage of the much larger web ecosystem, plugins and community and the relative ease of deploying and maintaining a website when compared to a native application in the respective app stores.
“For those who develop both on the web and mobile, you will appreciate that a website can be built in less time, that an API does not need to be maintained with backwards-compatibility (all users will run the same version of your website’s code, unlike the version fragmentation of native apps and that the app will generally be easier to deploy and maintain,” writes Ferrugia.
Now all of this is real and there’s quite a maker movement driving the notion of the PWA and we might well include Gmail offline as a prime example.