Difference between revisions of "PWA initiators"

From MgmtWiki
Jump to: navigation, search
(Context)
Line 5: Line 5:
 
* The goal of the PWA is to eliminate the need for native apps. While it is likely that some functions, like access to the keystone, will not be available for PWA, many other features a being added.
 
* The goal of the PWA is to eliminate the need for native apps. While it is likely that some functions, like access to the keystone, will not be available for PWA, many other features a being added.
 
* This page is specifically interested in tracking the ways tat a PWA service worker can be initiated from the browser (which includes some other PWA.)
 
* This page is specifically interested in tracking the ways tat a PWA service worker can be initiated from the browser (which includes some other PWA.)
 +
 +
==Solutions==
 +
 +
===PWAs as URL Handlers===
 +
* [https://github.com/WICG/pwa-url-handler/blob/main/explainer.md Explainer]
 +
* This is designed to give more control to the PWA for registering URLs tat can be accessed from native apps running on the phone.
 +
* In particular the PWA can register for URLs that are not it its own scope. The new feature is that this is handled in the browser and not in the o/s so tat all platforms will work the same way.
 +
* But they want to have their cake and eat it too, so the o/s will field such a link. The issue seems to be Android using WebAPK . Because WebAPK s are recognized by the Android OS, Chrome PWAs are able to fully integrate with OS features like the app picker.)
  
 
==References==
 
==References==
  
 
[[Category: Profile]]
 
[[Category: Profile]]

Revision as of 20:13, 21 March 2021

Full Title or Meme

This is an extension to the wiki page Progressive Web App to track evolving changes to the ways that PWA are initiated.

Context

  • The goal of the PWA is to eliminate the need for native apps. While it is likely that some functions, like access to the keystone, will not be available for PWA, many other features a being added.
  • This page is specifically interested in tracking the ways tat a PWA service worker can be initiated from the browser (which includes some other PWA.)

Solutions

PWAs as URL Handlers

  • Explainer
  • This is designed to give more control to the PWA for registering URLs tat can be accessed from native apps running on the phone.
  • In particular the PWA can register for URLs that are not it its own scope. The new feature is that this is handled in the browser and not in the o/s so tat all platforms will work the same way.
  • But they want to have their cake and eat it too, so the o/s will field such a link. The issue seems to be Android using WebAPK . Because WebAPK s are recognized by the Android OS, Chrome PWAs are able to fully integrate with OS features like the app picker.)

References