Progressive Web apps
PWAs seek to produce the same user experience as that of a native app, but rather than downloading an application, a PWA employs your browser. PWAs attempt to tap into the best of both worlds. They intend to leverage the benefits of Web apps, such as their HTML base and cross-platform availability, while still addressing their shortcomings, including their UI and touch, personalization, access in low to no bandwidth situations and deployment to the home screen.
Additionally, the application shell framework and the service worker make all of this possible.
Using the Web manifest, a Web page may register the service worker with the browser. The Web page then begins talking to the service worker, not the Web server. The Web page stops worrying about the Web server in question; it simply makes a request to the service worker, and the service worker provides a response dependent on the PWA developers’ requirements.
Service workers have a state unlike the general Web. They are able to respond to push notifications from the back-end Web server, sync background data, receive updates, maintain cached data, and provide an experience for the front-end PWA so that the app may work even with no bandwidth.
The app shell and the service worker come together to increase both speed and functionality. While the app shell provides a native-like interface in terms of UI and design, the service worker provides the glue that allows the overall PWA to be responsive and quick.