In this guide, I'll cover how to get started with Progressive Web App (PWA) development, including how to set up your app, use Lighthouse audits, register a service worker, add home screen compatibility and include push notification features.
Getting Started with Progressive Web App Development:
Progressive Web Applications (PWAs) are performance-based websites that have been streamlined to provide a superior mobile-experience, similar to that of an app.
They’re responsive, use less storage space and data, support push notifications and can be saved to the home screen on mobile devices.
Having recently developed a PWA in one of our app development projects, I wanted to write a step-by-step guide that would give beginners everything they needed to know to get started:
Setting up your app
Using Lighthouse audits
Registering a service worker
Enhancing progressive nature
Adding home screen capability
Including push notifications
1. Setting up your app
First up, you need to create your project or find an existing project that you want to make PWA compliant. If this is your first PWA, I’d recommend keeping it simple for now so that you can focus on the PWA side of things. Your project can be built in any framework of your choice, I built mine using Vue.js as it is a lightweight framework and the CLI comes with a lot of PWA support straight out of the box.
2. Using Lighthouse Audits
Google Lighthouse is a free, open-source software which is available in the ‘Audits’ section of Chrome Dev Tools. There are several different audit categories that you can run against your website, including whether it meets the standards for a progressive web app. The audit lets you evaluate your app based on their PWA criteria and provides a checklist of improvements that need to be made. You may find that a lot of the recommendations are best practice when building websites such as using https, however there will be a few additional things that you need to consider and add to your project. I will detail some of these in the steps below.
3. Registering A Service Worker
One of the criteria for making your app PWA compliant is registering a service worker. This is the technology that enables your app to use progressive web app features that would normally require building a native app, such as offline functionality, push notifications and the ability to add shortcuts to the home screen.
Service workers are a script that your browser runs in the background (separate from your webpage), which have the ability to intercept and handle network requests, including managing a cache of responses.
In the image above, you can see that the service worker acts like a proxy between your app and the network. The service worker can check if a user is connected to the Internet and grab the latest data from the backend, or if they aren’t, it will display the most recent cached version of the website instead meaning that your PWA can still work offline.
4. Enhancing Progressive Nature
5. Adding Home-Screen Capability
The whole point of PWA’s. This functionality is what allows users to save websites to their home screen and access them in the same way they would a native app. In order for the browser to display this add to home screen prompt on your app, you need to make sure that you have met the following criteria:
To use push notifications on your app, you will need to make use of two APIs: The Notifications API and the Push API.
The Notifications API lets the app display system notifications to the user, just like a native app does. The Push API allows a service worker to handle Push Messages from a server (I’d recommend using Firebase Cloud Messaging (FCM) if you want to quickly get up and running with your own project as it creates unique tokens to for each device and session). Below are the steps you need to take to get started with this functionality:
Your app must ask the user if they would like to subscribe to notifications – you can do this using the Notifications API
Handle the notification subscriptions using the service workers. Eg, inform your service such as FCM, that the user would like to subscribe to a particular topic, eg ‘hurricanes’ or ‘puppies’
The service worker listens and is ready to receive any message coming in from the server. E.g. if a notification is sent to all users who have subscribed to the topic of ‘puppies’, then the service worker will take that content and display it on the user’s device.
You can configure what information comes through in the notification, such as the title, body text, icon, link and even the vibration pattern the phone should make when receiving the notification.
Again, browser support is key here. At the time of writing, both the Push API & Web Notifications are not supported by Safari. I’d recommend keeping an eye on out for updates as there are rumours that it is on Apple’s roadmap.
The Pros and Cons of progressive web apps:
Don’t have to deal with app store approvals etc – though this could be a downside as it could lead to a slip in quality
Easier to install – don’t have the friction of users having to find your app in the app store, download it, etc
Search engines can crawl them so they will appear in Google searches
Linkable – just like a normal website which makes it easy to share content with people
Uses web technologies – for those with web dev backgrounds this is great as you don’t have to learn another coding language to get some great native app-like functionality
App like experience with offline functionality and push notifications.
PWAs don’t have all the same features of native apps such as access to contacts, Bluetooth or advanced camera controls
For obvious reasons, they’ll also miss out on traffic and exposure from the App Store
There will always be some degree of browser inconsistency
Progressive Web Apps consume a lot more battery-life than native apps
Cross app login is also unavailable with other apps like Facebook and Twitter.
If you think a PWA could help solve the problems your organisation is facing, or you’re trying to develop your own progressive web app and need some help or advice, get in touch with the team!
Published on November 15, 2018, last updated on January 7, 2019