Enterprise Mobility And Progressive Web App

What is Progressive Web App

What makes PWA

In a nutshell, a PWA app consists of HTTPS, a Jason based manifest file and a service worker running in the background.

Web App Manifest

This is a Json based information catalog about the web app/ PWA app. This file will have an application icon, app name to be displayed once it is installed on the device, short name and other information like background color etc.

Service Worker

It’s a JavaScript file which resides in your PWA app locally on the device. This basically runs in the background and acts as a proxy between offline cache and app or network/ web server and app.

Application shell

This an architecture approach that is used in most of the PWA app development where it can reliably and instantly load responsive web screens similar to that of native apps. The app shell refers to the locally stored resources that a web app requires to load in the user interface template. This is a highly recommended approach for companies who are migrating from their existing single page web app which are heavy on JavaScript-based development.

Offline Support

Offline support is a key functionality to develop something that is equivalent to a native app. Service worker programmatic way to cache app resources which helps in the faster launch as well as supporting features during low or no network areas. Unlike any other mobile web app, PWA app with offline support will have full user interface capabilities, it renders and scrolls complete web page without any additional loading based on the implementaion logic. Also, the PWA does not need to ping server for every request, hence this saves big time on the data usage, unlike normal mobile websites.

Pros and Cons of PWA


  • App discoverability is decentralized. You can’t go to app store find an app you are looking for; you need to know the URL or vendor website to access or download the PWA to the home screen
  • Overall raw performance sometimes lower than the native app
  • Not all the platforms like Windows, Google and Apple are putting a similar kind of effort in promoting or enabling features to support PWA.
  • Data sharing between apps or leverage another app as a quick tool is presently out of question.
  • There are some studies shows that battery usage on PWA apps is higher compared to the native app because of the use of web code.
  • Offline support is kind of limited and it varies based on platform as well.
  • In some cases, not all browsers behave in the same way for PWA.


  • PWA Supports all kinds of devices including devices like Chromebooks.
  • Native app like security wherein user needs to provide independent privileges to access any hardware features
  • Being website, providing offline storage feature is a big gain to avoid having to have connectivity for every launch or transactions. Ex: Flipkart kind of websites can store the catalog information downloaded unless there are any changes
  • Support for push notification kind of native app features.
  • Service worker kind of components helps apps to load quickly
  • Apps that are PWS candidates, money saved on development as well as for maintenance

Case Studies

Some of the major companies who either moved from native app to PWA or who built PWA app from the grounds up and some companies have converted their existing web apps to PWA apps.


One of the business needs for Pinterest was to make a good mobile website which can be accessible by the people who live in the low network area. More than 50% of Pinterest users are outside the USA.


When you go through PWA materials on the web, you would hear about BookMyShow and MakeMyTrip names everywhere. Even though over more than 80% of BookMyShow transaction happens on mobile devices, there were concerns raised on memory usage, load time etc., were not optimal for users. That’s when they decided to redesign their mobile web to have a PWA and solve some of the problems their native app users have as well as mobile web users.

Enterprise Mobility current state

App is still a need

Why do we still need an app? Still, the apps are key interface for people to get things done on the go, be enterprise user or a common man. Also, mobile is still a focal point of data collection, quick workflow execution. A device which everyone carries today! So, the app is still a necessity for everyone, be it for enterprise tasks or for personal work. The challenge has moved from building an app to how do you market it and how easy for people to find an app and install it on the device. Once it is installed, it depends on how quickly it launches and how easy the user interface is for someone do their task and get out of the app. These are all the factors I think Progressive web app carefully addresses to a larger extent today even though the platform is still evolving, and major OS/ device manufacturers are making it easy for Progressive web app to run on their platforms.

App maintainability

From a developer point of view or an enterprise point of view, maintaining an app is a key parameter they need to consider before making a decision on the platform in which they want to build the app or suite of apps.

App discoverability

According to some of the studies done recently, the data indicates that the majority of the users don’t download a single app from the app store in a month. App store is just becoming the graveyard of apps which people really don’t use the app store to find a certain type of app unless there are some external links provided by vendor or marketing channels pushes users to download it from the app store. Overall, as an app developer, you don’t need to submit an app to the app store or build and market it as another channel. The PWA app URL can be shared as a secured URL and save it onto phone’s home screens to use it like any other app be it offline or online.

Enterprise Mobile — Is PWA the right candidate?

Overall PWA may not be the perfect solution yet but like any hybrid app, they are getting popularity in the enterprise space addressing some of the concern’s enterprise had in terms of performance, offline support and security while adopting a non-native platform. Another advantage that enterprises are looking at is, converting their legacy websites to a PWA app and slowly migrate users to PWA and then eventually move out of native app support.


Overall, a good well designed PWA app can replace the company’s mobile website, native app and eventually desktop website as well. If you are an enterprise and still thinking about mobile strategy or in the process of reviewing the existing mobile strategy, then you should seriously consider PWA as your option.

Point of views around and beyond technology