…is now the right time to adopt a technology stack that will last no more than one or two years? Does it make sense to invest time and money learning dedicated and platform-specific knowledge in order to develop native applications (unless your app requires specific features or performance expectations)?<\/p>\r\n
“You are too concerned with what was and what will be.” <\/em><\/strong>(Oogway – Kung Fu Panda)<\/p>\r\n Believe it or not, pandas are still there. This time, however, they are following their own way of Kung Fu, and quoting Google they are finally taking the right vitamins<\/i> (oh! I forgot to say that by \u201cpandas\u201d I really mean the good old web pages, and the very browser you are staring at).<\/p>\r\n Simply put: what about adopting existing and emerging web application patterns to save time and money while delivering nonetheless quality services and apps?<\/p>\r\n That is, basically, a\u00a0P<\/b><\/strong>rogressive\u00a0W<\/b><\/strong>eb\u00a0A<\/b><\/strong>pp: a future-proof bridge between traditional native apps and web applications.<\/p>\r\n “Fascinating!” <\/strong><\/em>(Mr. Spock)<\/p>\r\n Ok, let\u2019s get serious. Turtles, pandas, and Star Trek characters sit down there in silence (for a while).<\/p>\r\n Disclaimer: technical jargon following.<\/p>\r\n PWAs are, at their core, nothing but responsive websites <\/em>on steroids<\/em>. Websites that can progressively enhance their features depending on the browser\u2019s capabilities. It\u2019s all about making the most out of the last improvements in web browsers to create a better user experience. A web app which can leverage the edge of available technologies, to deliver a native app like experience on a mobile device.<\/p>\r\n No magic or esoteric technologies here, apart a few experimental javascript API. Technically speaking a PWA simply is:<\/p>\r\n 1- any web site\/application served through HTTPS Now, since a progressive web app is nothing but a web application, there is no need for developers to distribute a PWA via proprietary repositories such as iTunes or Google Play. This is certainly a win-win for you and your users. In fact, no one is looking for your app on a store unless you are Facebook or Google Maps. Also, your users do not have to install yet another beefy app on their device: they will simply navigate to your webapp using their browser (with the option of an icon on the home screen \u2013 more on that later).<\/p>\r\n Sure, to develop a good and working PWA requires a lot of know-how. The reward though is that you are able to deliver an accessible, platform independent, no-install, no-updates, engaging app which your users are happier with. Luckily, publishing and promoting a PWA is as it is for any other web page I.e. a good SEO to target traffic to your app.<\/p>\r\n Intrigued?\u00a0<\/p>\r\n “Curiosity is the essence of our existence.” <\/strong><\/em>(Gene Cernan)\u00a0<\/p>\r\n Following Google’s advice, we can sum up an app in terms of\u00a0capabilities\u00a0<\/em>and\u00a0reach<\/em>.<\/p>\r\n Capability is at its best in native apps: they are fast, reliable, easily accessible from the home screen, and get full access to the device hardware. On the contrary, websites are ubiquitous, searchable, not controlled by a single private company, always up-to-date (no need to download or update from a store), and widely accessible by anyone anywhere.<\/p>\r\n PWAs sit at the intersection of the best features of both worlds:<\/p>\r\nProgressive Web Apps: a new hope<\/h3>\r\n
<\/em>2- with a valid app manifest<\/em>, and
3- a registered service worker<\/em> which implements a fetch event handler (with a minimum support for caching\/offline)<\/p>\r\nWait, but… why?<\/h3>\r\n
![\"\"](\"https:\/\/exmachina.ch\/images\/2020\/05\/diagram.png\" "\\"\\"")
<\/a><\/p>\r\n