WAM is the web runtime used in LG webOS (both for its products and the Open Source Edition), and has been adopted by Automotive Grade Linux. It is built on top of Chromium web engine and its Ozone Wayland backend.
In this presentation I will showcase its main features, and talk about its history, from HP/Palm devices, through LG TV and its Raspberry PI Open Source Edition, to end with its adoption in AGL.
WAM, also known as WebAppManager, or Web Application Manager, is a system service providing web runtime capabilities in LG webOS and AGL platforms.
Its goals are:
* Performance through reuse of resources among web applications.
* Provide a native-like experience to applications based on the Web Platform standards.
It has been a central part of LG webOS in all its flavours, including LG webOS Open Source Edition. As such, it provides a great example of how to integrate the web experience in a Linux system, providing graphics integration through Wayland protocol.
It will be a history of web engines. From QtWebKit, to QtWebEngine, to a custom embedding API directly on top of Chromium.
This is also going to be a history of the flexibility of the platform, as it was possible to integrate it not only on webOS, but also in the different releases of Automotive Grade Linux, even after different architecture rewrites. This presentation will highlight the strong points that make WAM specially flexible for integrating in different Linux platforms.
A retrospective of the main milestones of WAM in last decade. But also a look into its future.
