bodo-hugo-barwich / plack-pwa-web Goto Github PK

The concept of the App Shell means that the web page consists of a base frame which is mostly constant around the web site which downloads additional content with Lazy Loading JavaScript.
The JavaScript logic that displays the content on the web page is already implemented but the data it displays is statically written into the Source Code.
For an API First Architecture this data must be obtained from the API Backend.
The API Backend will manage all the Product Data which also means that Product Data and URLs must be validated with the API Backend.

With shipping the PhantomJS Executable to the Production Environment the disc space consumption has increased drastically.
The latest deployment to Production has failed
Glitch Production Deployment failed

So, for the Integration Test with PhantomJS the Executable must be directly downloaded into the Test Environment and cannot be shipped with the Repository anymore.

Some Design Elements do not work as intended in the Firefox Browser.
To achieve a uniform Design the List Cards and the List Grid need to be designed differently.

To perform Automated Tests in a Serverless Environment the tests must not rely on GUI Applications.
So the PhantomJS automation application can do the JavaScript interpretation that is needed for the Web to be completely working.

The Web Site Assets are statically stored in the Browser.
They are loaded into the Browser at the Install Event of the Service Worker.
The Demo at the Service Worker Cookbook shows that the Assets are never updated if the new Service Worker does not the Take Over.
Cache Refresh Exercise

Even the static Assets of the AppShell of the Web Site need to be updated to conserve the coherence of graphical and programmatic parts of the Web Site.
This is crucial for a correct operation of the Web Site.