Hello PWA lovers,
Jose and I are pleased to announce the release of SuperPWA version 1.6, here is the changelog.
A good share of the basic expectations for multisite network support was already done by a dear user @juslintek two months ago. Extending SuperPWA for multisite was a breeze.
However, figuring out the uninstall was challenging. Since day one, we wanted to be clean, both during install and uninstall. The only option SuperPWA adds to the database during install is its version, settings are saved only when the user clicks “Save Settings” the first time.
SuperPWA uses smart defaults to generate a manifest and service worker, so that your PWA is ready instantly on plugin activation. During uninstall, we always clean up everything we created leaving no trace behind.
In a multisite context, sticking to this standard was not easy, but we have a focus on quality, and we are determined to stick to it no matter what.
No easy routes here. SuperPWA will clean up after itself even on a multisite.
Note: If you network activate SuperPWA, manifest and service worker are generated on the first visit to the WordPress admin of the respective site. More on that.
Progressive Web Apps need HTTPS. Sometimes when users redirected HTTP to HTTPS using a third party plugin, the URLs were still HTTP at the time of manifest generation.
Few users were facing issues and with release we want to get rid of this trouble once and for all.
Even if you are redirecting your website using a plugin, your manifest and service worker will always have HTTPS links from now on. We got that covered!
Bye bye HTTP, hello HTTPS!
SuperPWA started using my WordPress starter plugin as the base. But it was time to move beyond to accommodate for growth.
And so we did. Here is what the new structure looks like:
As always, we welcome your feedback. We would also love to hear how you are using your PWA’s and how we can help you make it even better.
Over to you.