10 Comments

  1. Ciprian Popescu

    I switched my manually coded implementation with this plugin. Chrome’s Lighthouse says it’s poorer than my implementation and it’s missing the “Add to home screen” feature. But I’d rather have it as a plugin than hardcoded in my theme and I hope they’ll update it more frequently.

    Report

  2. Peter Shaw

    This gets an article and the 5 existing plugins, including mine, which are far better than this get no publicity whatsoever.

    Report

  3. Tim Kaye

    “This PWA feature plugin is intended to equip and facilitate other plugins which implement PWA features,” Ruter said. “It’s not intended to negate any existing plugins with these features, but rather to allow such plugins (and themes) to work together seamlessly and expand upon them.”

    Interesting that core developers are suddenly so interested in having different plugins work seamlessly together. After all, the Gutenberg architecture rejects that approach entirely. See https://github.com/WordPress/gutenberg/issues/4116

    It’s almost as if what is getting proposed for core is determined not by its substantive value but according to the whims of those with the power to commit it.

    Report

    • Weston Ruter

      Gutenberg is absolutely being designed to let plugins work together seamlessly. The issue you’re linking to is regarding backwards-compatibility with existing plugins that manipulate content. In this case, Gutenberg needs to provide a common API for plugins to interact with the blocks. It’s the exact same thing for PWA features: core needs to provide a common API for plugins seamlessly to extend the web app manifest and the service worker. In the case of the PWA plugin, however, there isn’t really a concern for backwards-compatibility since it is a new technology.

      Report

      • Tim Kaye

        Weston,

        You are the person who told me on this site a couple of years ago that the Customizer was still a work in progress, and shouldn’t be criticized too much. And yet it remains clumsy, brittle, and the width of a cellphone screen.

        So let’s look at what is actually said in the thread to which I linked. John Blackbourne comments that Gutenberg works in such a way that “almost completely eliminates the ability to interact with blocks beyond the block editor.” While Andrew Duthie concedes the point and reminds everyone that “for better and worse, we settled on HTML as the ultimate source of truth.”

        It is, of course, for worse. If Gutenberg were really being designed to make things work seamlessly together, it wouldn’t be relying on HTML comments.

        Report

      • Weston Ruter

        The Gutenberg issue is not closed yet. Work is still underway.

        Anyway, this is about PWA not Gutenberg. The purpose of the PWA plugin is to allow themes and plugins to have a common API so that they can work seamlessly together in how they need to make their respective changes to the web app manifest and the service worker.

        Report

      • Pete

        Whilst a canonical manifest is almost certainly beneficial I’m not convinced that it is needed or a good thing to handle the service worker side.

        Service workers are just so powerful and flexible and people’s needs are so different. The permutations are practically infinite.

        Report

Comments are closed.

%d bloggers like this: