Progressive Web Apps Aren’t Mobile Apps

And if you think they are, you are going to have a bad time.

Progressive Web Apps (PWAs) hit the scene promising fast and reliable experiences to users without having to use a web browser or visit the app store. They were the theoretical answer to the discoverability problem of native apps and the reliability issues of responsive websites. However, depending on the version of iOS or Android you are using when you access a PWA, you may have a relatively full featured experience or a severely handicapped one. So what are the advantages and limitations of PWAs and when should you use them?

What is a PWA, anyway? It can be hard to get a straight answer. Some web technologists will die on the hill saying they are not websites, even though they are built using web technology. But are they really apps?

Technical differences between Apps, Websites, and PWAs

Native Mobile App	Website	PWA
Software, typically written in Swift for iOS or Kotlin for Android that complies natively on a device.	Code that compiles in a browser, typically written in HTML, CSS, Javascript, and other front-end languages.	Written in HTML, CSS, Javascript, or other front-end language.
iOS and Android apps will have separate code bases.	One codebase will serve all web browsers across devices.	One codebase will serve both iOS and Android.
Has access to low level hardware integration. This allows you to use things like bluetooth, push notifications, or system level password management tools in your app.	Depending on the version of Android or iOS you are running, you may have a decent amount of integrations or basically none.	Depending on the version of Android or iOS you are running, you may have a decent amount of integrations or basically none.
Need to download from the App or Play Store.	Access via browser – either searching or web URL.	Generally accessed via browser in the same way you’d view or find a website. On Android, PWAs can also be listed in the Play Store.
Tap an icon on your home screen or app list to launch.	Must access via web browser. Both Android and iOS allow any website to be bookmarked to your home screen, but they will open in a browser view.	Tap icon on your home screen to launch. Browser chrome will not be used on a PWA launched from your home screen.

Because PWAs and websites use the same technologies, they have a lot of the same qualities. The performance of PWAs ultimately hinges on how much your OS version supports them. This can greatly limit access to features or functionality to your users in ways that you are less likely to experience with native mobile apps.

Why should you consider a mobile app?

Not every business needs a mobile app. As appealing as getting in the App or Play Store may be, your app needs to offer concrete value to your audience or it will be a waste of time, effort, and money.

• Native mobile apps shine when you want to offer a focused experience that has recurring value. They should focus on completing one or two specific tasks and should earn their place on your phone.
• Apps are great for connecting with the broader ecosystem on someone’s device or for using device specific features.
• App users tend to have a higher level of loyalty and engagement with a brand than people who only engage via the web. Assuming, of course, that the app is usable, valuable, and performant.
• Native app UI should be tailored to the specific device they are running on.
• Apps are software that need to be maintained in order to offer their full value. This means having iOS and Android developers on staff or finding a partner that can offer ongoing development support. It also requires you to update your software at least twice a year to support updates and changes to the hardware and OS (although you should update more frequently).

Why should you consider a website?

Nearly every business or product should have a website. Even if your business is 100% app centric, you will need a website to help people connect with and share your product outside of the App or Play store.

• When built correctly with a solid content strategy, websites are very discoverable. Websites shine when people are looking for an answer to a problem or need to complete a one time/infrequent task.
• Websites are not good for experiences that need hardware integration (like bluetooth) or for very redundant activities or tasks. The web has its strengths and weaknesses for different types of engagement and tasks.
• Websites tend to be more transient and can often be one stop on a user’s greater journey. There are tons of strategies to maximizing how you fit within that journey, depending on your audience and business goals. An exception is web apps, which are more functional than the typical website (think Google Docs) and serve a very specific purpose or function.
• UI for a website will be the same regardless of the device you use to access it.
• Websites also need to be maintained, but aren’t as tied to cyclical software and hardware updates like mobile apps are. Your website still needs to be reliable, speedy, and helpful, or it will quickly lose traction. You also don’t have to deal with the App or Play store when building or updating a website.

Why should you consider a PWA?

It is much harder to pinpoint the clear value of a progressive web app. They are more discoverable than an app, but there are definitely limitations and considerations.

• PWAs are “installed” on a users device by hitting the “share” button on Safari or the “menu” button on Chrome then tapping “Add to home screen”. This requires a user to intuitively know something is a PWA. Some experiences will have banners on android promoting the fact they are PWAs, but many don’t, and those banners do not display on iOS.
• The UI for your PWA will generally be the same for both iOS and Android.
• PWAs have more system capabilities on Android that make them feel more like an app. Unfortunately, iOS does not have the same amount of support (as of June 2019). There are a few features supported on both iOS and Android : offline mode, audio and video capture, access to files on a device, and some inter-app communications. If you are considering building a PWA, it is important to know what the web can do on a given device.

What about instant apps?

Compared to PWAs, instant apps feel like Android’s little secret. Instant apps allow users to engage with your actual mobile app through the web without having to download the whole experience. This is the direct answer to PWAs, but using native mobile technology.

• Instant apps should be smaller than 4MB (for non-game experiences) and are discovered through a banner on the web. Instant apps are loaded from the browser, but push to a full app experience outside of the browser.
• There are some hoops to jump through to set them up and iOS users cannot take advantage of this feature right now.
• Google has renewed their support of instant apps, but this capability is still relatively unknown. They could be a viable option for businesses who already have an app, but want to ensure it is easy to access and use.

Sorry, PWAs aren’t the app killer

On paper, there is value to PWAs, no doubt. They promise a better web experience, but I have yet to see anyone deliver on the promise. It can be healthier to think of PWAs as an enhancement to your web experience, rather than a replacement for an app. Not all products or companies need apps! If web is your primary digital touch point, focus on making your website experience fast, accessible, and useful. Despite the push for PWAs to be the future, they aren’t mature enough to compete with a solid native mobile experience for products that would benefit from a mobile app.

60