Install an extension to have The advantages of PWA:
The user does not have to install it (so there is no installation time or updates)
Install an extension to have It’s cross-platform and cross-device
- Extremely fast loading pages
- Can work offline and user can make notifications when he loses his connection
- Progressive improvement depending on the device
On the other hand, PWAs are complex to set up.
Daniel advises against using existing WordPress phone number library plugins for PWAs because they have plenty of flaws. A PWA is a huge plus, but only if it’s done right.
If you make a PWA with an extension, it will need to be fixed
Or you can code it yourself, but be aware that it will take a lot of time. In this case, Daniel recommends using the WordPress REST API to send and receive data in the right format, and “playing around” with the following hooks:
- stylesheet
- template
- theme_root
- theme_root_uri
Can we combine PWA and AMP?
The problem with AMP is that it limits the way content is rendered (features, scripts, etc.). PWAs have significant advantages for users: sending notifications, caching, etc.
It turns out that PWA and AMP can be combined, and Google even recommends it.
To do this, you first need to set up AMP (and memberpress vs wishList member: which is better? make sure to make any necessary corrections). And once AMP is working, Google is finding your content, etc., you can apply the PWA Worker on top.
AMP helps attract users to your site, and PWA keeps them loyal.
To recap how to truly make WordPress compatible for all mobile devices, Daniel advises:
Have a responsive site
- Train those who manage the site on a daily basis
- Implement the AMP
- Add a Progressive Web App
- (Optional) Switch the entire site to PWA (or have clean email a mobile site in PWA and a normal site for desktop).
Finally, Daniel recommends Google Lighthouse to ensure your site complies with all PWA guidelines.
We thank Daniel for his contribution, which was rich in quality information and useful advice.