Progressive Web App - Revision history

Tom: /* Other Reference Material */

2023-10-25T19:25:07Z

‎Other Reference Material

2022-09-21T01:19:32Z

‎Developers still seem to favor Native Apps

2022-09-15T01:30:57Z

‎Other Reference Material

2022-05-30T23:18:46Z

‎Developers still seem to favor Native Apps

2022-05-30T22:43:56Z

‎Developers still seem to favor native apps

2022-05-30T22:41:45Z

‎Problems

2022-04-08T17:03:29Z

‎References

2021-11-19T04:45:24Z

‎Declarative Links

2021-11-19T04:45:00Z

‎Declarative Links

2021-11-19T04:44:17Z

‎PWA initiators

@@ Line 19: / Line 19: @@
 ===Developers still seem to favor [[Native App]]s===
-* Some APIs, like access to the secure enclave, (in 2022) are not available to PWAs
+* Some APIs, like access to the [[Secure Enclave]], (in 2022) are not available to PWAs
 * because they have no way to discover the PWA’s
 * because some vendors are holding back the web by not allowing certain features (or whole engines for that matter) on their platform.

@@ Line 63: / Line 63: @@
 ===Other Reference Material===
 * The [https://trustregistry.us/ web site Trust Registry for the US] is constructed to load as a [[Progressive Web App]].
 * The [https://appsco.pe/ web site App Scope] attempts to list the [[Progressive Web App]]s but is always a little bit out of date.

@@ Line 19: / Line 19: @@
 ===Developers still seem to favor [[Native App]]s===
 * because they have no way to discover the PWA’s
 * because some vendors are holding back the web by not allowing certain features (or whole engines for that matter) on their platform.

@@ Line 18: / Line 18: @@
 * The PWA offers considerable speed-up for parts of the [[Web Site]] including the home page. This can make display of some content out-of-date and this needs to be understood and perhaps mitigated by the [[Web App]] programmer.
-===Developers still seem to favor native apps===
+===Developers still seem to favor [[Native App]]s===
 * because they have no way to discover the PWA’s
 * because some vendors are holding back the web by not allowing certain features (or whole engines for that matter) on their platform.
 * Worker at reddit claims they get much higher retention in-app even controlling for things you would expect to confound.
-*Data from this [https://areknawo.com/web-vs-native-make-the-right-choice-in-2021/ link]
+*Data taken from this [https://areknawo.com/web-vs-native-make-the-right-choice-in-2021/ link]
 ==Solution==

@@ Line 48: / Line 48: @@
 * Traditionally PWA were created by web sites that wanted to have some continuing presence on the browser even when the web connection was inoperable. If the web site was accessed, the service worker of the PWA would start up immediately and call out to the web site as needed for updates.
 * As new methods are being introduced they are being tracked on the wiki page [[PWA initiators]].
-==Declarative Links==
+===Declarative Links===
 almost all launch use cases can be covered by a handful of fixed rules (for example, "choose an existing window in the same app, focus it, and navigate it to the launched URL"). Thus, this proposal, "Declarative Link Capturing", allows sites to choose one of those fixed rules without having to implement custom launch event logic, which should satisfy most use cases, and simplify the implementation in the browser and in all the sites.
 * [https://github.com/WICG/sw-launch/blob/main/declarative_link_capturing.md explainer] is evolving and seems to be settling down by the end of 2021.