Progressive Web Apps (PWAs) Part 5: To PWA or Not to PWA?
Click Here To Start With Part 1: The Limitations No One is Telling You See
OUR TAKE: Not To PWA*
*There are a few exceptions we cover below.
For most use cases, we believe that the seemingly “minor” user experience issues can add up to make a big difference. Progressive Web Apps simply cannot offer many of the core elements that make native apps so great.
Unless your audience is so targeted that you can help every customer through the experience of using a PWA and you fully understand the limitations, the risk to your user adoption and revenue impact is too great.
A Progressive Web App IS an Optimal Architecture In These Use Cases
If you happen to fall into these edge-case scenarios, we can see using a Progressive Web App.
- If your audience is 100% Android only. PWAs are much more functional on Android. In fact, if PWAs functioned on iOS as they do on Android, this would be a whole different post!
- If you can help each and every user through the process of setting up and using your PWA, guaranteeing it’s adopted and used as you intend.
All this said, we’re not saying full native is the answer every single time. If you’re looking for a cross-platform experience, we recommend React Native.
THE BOTTOM LINE
Cost savings do not matter if no one uses your Progressive Web App. Evaluate alternative architectures and code bases, such as React Native, to balance cost savings with the optimal user experience and native feature offerings.
What do you think about PWAs versus React Native? Let us know in a comment below.
Leave a Reply