Do WordPress PWA plugins deliver on anything that PWAs promise?
Do they even live up to their stated functionality?
A PWA is supposed to provision for off-line reading and functionality.
1. Offline rendered pages for a disconnected “online” experience.
2. Offline payments
3. Offline in-app navigation from page to page.
4. Offline interactions with content.
Yet the real world implementation of a PWA appears to merely inform end-users that they are currently offline. Browsers do this.
And from my limited experience, a PWA will only store a page that has already been visited and in the event that an end-user follow a link to another in-app page they will come face-to-face with an off-line message.
Do PWAs for WordPress place the onus of page storage on the user?
Does an end-user really have to visit every page that they anticipate wanting to read off-line in the future? And must they put up with those visited pages containing no images?
Am I wrong about PWA? Based upon theory alone, PWA is something I want to implement for my audience with great enthusiasm on my end. The reality, however, has yet to demonstrate any practical value of PWA to me or to audiences.
I know that a PWA allows me to add a bookmark to my home screen, but I can do that with any non-PWA website. Plus I can just create bookmarks in Safari – a bookmark is a bookmark.
I may be missing something, but I have to ask the question after experimenting with six different PWA for WordPress plug-ins: Do current PWA offerings bring anything of functional value to the table?
What functionality are you providing via PWA plugins (without having to do additional work because the plugin isn’t doing it for you)?
[ad_2]