Today, we install an app on our mobile phone using the app stores available for each operating system. This process allows us to find our favorite apps and companies, like Apple and Google, use this model to make money.
The mobile apps appeared with the intention of adding functionalities to a mobile phone. Apps work more closely to the hardware, so it’s more easy to do software that uses things like GPS, Blueototh, NFC, Accelerometer, etc. This provides rich applications to users and better user experience in detriment of using a browser. However, in the last few years, the web browsers and web technologies (like JS frameworks) evolved a lot!
The Progressive Web Apps (PWA’s) appear in this context. Basically consists on Rich Web Apps with the functionalities of the mobile devices. In a simple way, imagine an Web App with GPS or bluetooth functionalities… Today, web browsers doesn’t show only websites, they show rich apps that can be even more rich with some of the features of PWA’s.
PWA’s could be the next big thing on web development. It could redefine the way we use mobile apps and the way we explore the web.
Nowadays a company that pretends to offer a complete software solution has to worry to hire specific resources to accomplish the mobile and web developments. Beyond this, the server API’s also may need to adapt to each client component. On this situation, companies has to hire different specialists to accomplish the all solution. This means more money and more time to market. The PWA’s tries to minimize this problem. In a simple way, you develop one time, and the solution will work on any kind of device. It is an website which may have app features. On this way you only need one team to build all the client solution.
Another advantage consists on the installation process of a mobile app. Today, a user must take some steps before start using the app: go to the app store, search by the app, install, authorization to install… All this steps has the consequence of loss of potential users. Every Step Costs You 20% of Users
PWA’s can also minimize this. You use a PWA like a webpage access, so you don’t need to access to an app store. Also, we do not have to worry about updates to each application anymore.
Today, a user visits an average of 100 unique sites per month, but spends 10 times less on a site than an app. However, the time spent on apps is only done on the same 3 or 4 apps. PWA’s try to bring together the best of both worlds, users spending more time on the app (such as mobile apps) and easier access to more apps (just like traditional websites).
In technical terms, the role of the Service Worker is the hallmark of this new standard of development.
Currently, not all browsers support Service Worker. However, everything indicates that it is a matter of time. Chrome, Firefox or Opera are some of the browsers that already support this technology. Support for Microsoft’s Edge is under development and there are already some indications that Apple supports technology in Safari.
Some features of PWA’s are:
- Compatible with any device. (as long as the browser supports it)
- Fast loading! (probably at first load may be a bit slower if compared to a native application)
- It is responsive and so adapts to any screen.
- Native appearance. “Same as an app… “
- No installation required. (And you can add a “link” to your smartphone’s home screen, simulating access to current mobile apps)
- Works Off-Line! (Thanks to Service Worker)
Resistance to Change
There seems to be only advantages with PWA’s, but for mobile application mediators it may not be very enjoyable to end up with their stores. Nowadays, the stores bring a lot of money to Google and Apple. With PWA’s, new business models will have to be introduced…
There are already many applications with PWA technology. Some examples can be seen at this link: https://pwa.rocks.
Google currently has a site that helps you understand PWAs in more detail. It’s interesting to see the investment that Google makes in trying to steer the market to this new standard. Even when this seems to go against the Android application store. On the other hand, it could be a bet on cloud services (like Firebase) to deploy your PWA’s.
Personally, I am very interested in this area. I always liked watching the evolution of the web and I’ve always been curious about the mobile. I did not deepen on mobile development because if I’m going to develop some app, I would have to launch one version to all systems. I would have to invest a lot of time, to build one app to different systems and I wouldn’t be good on any of them. Although later discovering solutions like Ionic, I ended up not having the opportunity to invest the time that I would want in this type of frameworks.
This was a little introduction to PWA’s. I hope you like.