Hi Konstantin,
I love the concept of your plugin. As a CDN it seems to work perfectly.
It would be awesome if we had the option to use this ONLY as a CDN – as it stands now. In other words, the “service worker” and “PWA” options could be enabled or disabled.
Otherwise, from the PWA perspective . . . it is difficult to figure out. There are some settings in the plugin and some settings in the Baqend dashboard. Unfortunately both areas are really lacking in documentation. And the plugin itself is lacking in ease of settings / setup.
While you do have the “guide” it seems to mostly focus on the API and is written for tech savy people rather than the rest of us. – It does appear, via the API, it is quite extensive, but a person has to understand the API coding, where to enter it and how to customize it.
I like Super PWA because setup is so easy, it is well documented and it is built to work with OneSignal Push Notifications. You enter your settings and the plugin takes care of the coding.
I see that yours can also do push notifications, but the whole setup of it is confusing. I can’t figure out if it requires the use of a push notification service (like OneSignal) or not. Or whether there are tracking and statistics. Or if I can segment the subscribers.
Again, I do think your plugin / service is a groovy concept, but I’m having a hard time figuring out how to use it. Where Super PWA makes it very simple to set up.
Unfortunately, it looks like I’ll end up having to remove yours (sorry!), set up a CDN and use Super PWA with OneSignal to get the results I’m after.
Is it possible to use your service as a CDN ONLY(!) on WordPress? I do like how that part of it works.
Thank you,
Rhonda (aka LL)
