Progressive Web Apps
Progressive Web Apps, PWA, are the newest form of Apps which are now termed Native Apps to avoid confusion.
Progressive Web Apps are derived from programs that used to be written as extensions, or plug-in, for a Web Browser. Like the extensions these are often written in Java. The differ from extensions in that the scope of the full Native App is usually larger where it would replace a full program of possible complicated functions and will often support multiple screens. Therefore they can have access to some device APIs and functionalities that only native mobile applications are expected to be able to access and also have the operating system’s native interface.
 The advantages
The basic idea is to make the app run on a Web Browser that the user already has and is familiar with. The same app is intended to run on various platforms with different OS's. Unlike a regular use of a Browser it may run on a local machine without Internet access, although this is not always a requirement of the app. Using the web may allow the use less local resources. The web may also allow automatic syncing of eBooks allowing you to stop reading on one machine and pickup where you left off on another.
 The disadvantages
It will normally use more power that a fully customize app. It is likely to also be slower since it needs to be interpreted instead of being compiled. The App itself needs to be available on a server that is accessed on the web. Although once started it may run locally. Not everything can work the same depending on features from the OS.
 Source languages
- Polymer: A combination of components, tools, and templates primarily for building Progressive Web Applications.
- Accelerated Mobile Pages (AMP): An open-source project for improving the performance of web pages by making them load almost instantaneously.