When Google says something is the next big thing, we tend to listen.
And Progressive Web Apps (or PWAs) are, in a word, it.
If you missed this news and were absent the day they had the PWA meeting at work, here’s what you should know.
The nutshell version.
PWAs can be summed up as a web page that can be hot-linked to the homescreen of the user’s phone, creating an app-like experience. Some recent technology enhancements and the increased power of newer smartphones and devices make it possible.
In slightly more technical terms, think of a PWA as a hybrid utility – a mix between a website and a native application on a mobile device.
Thirsty for an example? Here’s an example of a simple PWA that allows users to learn more about beer. Cheers.
Top 10 reasons they’re a good thing
Google (and us for that matter) like PWAs for these reasons.
- PWAs are fast to load
- They feel like an app
- They don’t require an app store to install
- They build search engine visibility
- They’re responsive
- They work with all browsers
- PWAs are linkable and not be hard to install
- They’re enhanced to work offline or on low-quality networks
- They stay fresh because of a background update function
- PWAs are safe and served via HTTPS
If you need a laundry list of PWA attributes, look at this detailed look at what Google says are the key elements of a good PWA.
How PWAs keep users engaged.
Studies have shown that in a consumer mobile app, you lose around 20% of the user base for every step a user has to perform before getting to valuable content or experiences.
It’s called the “funnel effect.” And it has huge implications. For example, what if the user has to do any of the following?
- Go to the app store
- Download the app
- Open App
- Sign up for the app
- Create something
- Post/Send to friends
- Overcome any other typical experiential roadblock
If each of these steps causes a 20% drop in users, the attrition rate is ridiculous. With PWAs, the first three steps are bypassed, allowing users to find value quicker and stay engaged longer.
Loading & Pushing.
People expect a site to load in 2.0 seconds or less, according to study. After 3.0 seconds, many are gone. Now think of a phone on 3G trying to load the heavy elements of a website. The words “clunky,” “glacial,” and “stultifying” come to mind. PWAs, by contrast, load quickly even in areas with poor connectivity.
Another great PWA feature is the ability to send Push Notifications to users who have added the PWA to their phone. Push notifications can increase CTR by up to 40%.
And now, for PWA drawbacks…
Since Google began leading the push for PWAs in 2015, development has been slow.
Cutting edge browser technologies are needed for a PWA to function correctly. Sure, the PWA most likely will still work on older devices and browsers, but the UX won’t be the same.
Apple is developing the required pieces for PWAs to function 100% correctly on iPhones and other iOS products. And because PWAs function similar to a normal website, a user on an iPhone can still reap the benefits of the PWA, even if they are unable to add it directly to their homepage.
Source links:
[1] https://www.smashingmagazine.com/2016/08/a-beginners-guide-to-progressive-web-apps/
[2] https://developers.google.com/web/fundamentals/getting-started/codelabs/your-first-pwapp/
[3] http://blog.gaborcselle.com/2012/10/every-step-costs-you-20-of-users.html
[4] https://blog.kissmetrics.com/speed-is-a-killer/
[5] http://andrewchen.co/new-data-on-push-notification-ctrs-shows-the-best-apps-perform-4x-better-than-the-worst-heres-why-guest-post/
[6] https://jakearchibald.github.io/isserviceworkerready/
