PWA

Descripción

Progressive Web Apps are user experiences that have the reach of the web, and are:

  • Confiable – Carga inmediatamente y nunca muestra el downasaur, incluso en condiciones de red inciertas.
  • Rápido – Responde rápidamente a la interacción de usuario con animaciones suaves como la seda y sin desplazamiento a tirones.
  • Cautivador – Se percibe como una app natural en el dispositivo, con una experiencia de usuario inmersiva.

This new level of quality allows Progressive Web Apps to earn a place on the user’s home screen.

Sigue leyendo más acerca de aplicaciones web progresivas (PWA) en Google.

En general, un PWA depende de las siguientes tecnologías para estar disponible:

Este plugin sirve como un lugar de encuentro para dar soporte a aquellos en WordPress que tienen la intención de que sea propuesto para un merge con el core , pieza a pieza.

This feature plugin is not intended to obsolete the other plugins and themes which turn WordPress sites into PWAs. Rather, this plugin is intended to provide the PWA building blocks and coordination mechanism for these themes and plugins to not reinvent the wheel and also to not conflict with each other. For example, a theme that implements the app shell model should be able to extend the core service worker while a plugin that provides push notifications should be able to do the same. Themes and plugins no longer should have to each create a service worker on their own, something which is inherently problematic because only one service worker can be active at a time: only one service worker can win. If you are developing a plugin or theme that includes a service worker, consider relying on this PWA plugin, or at least only use the built-in implementation as a fallback for when the PWA plugin is not available.

In versions prior to 0.6, no caching strategies were added by default. The only service worker behavior was to serve an offline template when the client’s connection is down or the site is down, and also to serve an error page when the server returns with 500 Internal Server Error. As of 0.6, there is a new “Offline browsing” toggle on the Reading Settings screen in the admin. It is disabled by default, but when enabled a network-first caching strategy is registered for navigations so that the offline page won’t be shown when accessing previously-accessed pages. The network-first strategy is also used for assets from themes, plugins, and WordPress core. In addition, uploaded images get served with a stale-while-revalidate strategy. For all the details on these changes, see the pull request.

Documentation for the plugin can be found on the GitHub project Wiki.

Development of this plugin is done on GitHub. Pull requests welcome. Please see issues reported there before going to the plugin forum.

FAQ

Please see the frequently asked questions on the GitHub project wiki. Don’t see an answer to your question? Please search the support forum to see if someone has asked your question. Otherwise, please open a new support topic.

Reseñas

5 de febrero de 2021
Hi, Thank you for this great plugin it works for me on WP/BP. This is an amazing idea, and it works with W3 Total Cache too. Do you have any suggestions for me, how to implement a feature as "add website to home" when a user uses an iPhone or android? Thank you 🙂
Leer todas las 16 reseñas

Colaboradores y desarrolladores

«PWA» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«PWA» ha sido traducido a 7 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «PWA» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

For the plugin’s changelog, please see the Releases page on GitHub.