Are you developing code for integrating wbAMP pages / joomla content into progressive web apps.?
Big question! currently no. We have this in mind of course, and it is one of the main reasons for the "standalone" mode that wbAMP has. The issue here is really to define what a "standard" PWA could do, can this be generic? Of course, the default would be to simply cache content, so as to provide offline access, but that would be a rather limited scope.
We need to think this through (quite) a bit more...
Please let me know how to get those millions, any clue appreciated
Can the "Scope" of the PWA can be controlled by url differentiation as in */amp vs. /pwa/*/amp and maybe ?Yes and no. Inside the PWA you can of course decide what to do with the current page but one of the reasons we have not really pushed forward on this is that there can be only one single PWA loaded per domain.
It means that if wbAMP loads a PWA for yoursite.com, Joomla or other extensions cannot install their own. Or the other way around, if an extension already installed a PWA on your site then wbAMP cannot install its own.
The only way to work around this would be that Joomla itself has its own APi for PWA and it is Joomla that installs the PWA. Then extension should have a mechanism to register their own code to the Joomla PWA, to be able to perform their duty. I have not seen any talk about doing something like that so far.