Optimize the HMI

The HTML5 HMI is large and can potentially take a long time to launch. The HTML5 HMI layer includes the Browser Engine (also called the Web Engine or Web Launcher), HTML5 application framework, the Navigator (also known as the Applications Window Manager), and the HMI Notification Manager.

A couple of key techniques help to speed up the launch of the HMI:

To optimize the brower engine, all large browser libraries are loaded in a secondary IFS. Using the utility mount-ifs, the browser engine can read these large libraries from the disk much faster than from a regular filesystem.
The browser engine can run as a zygote and applications can be forks of the zygote process, so can use the libraries that are already loaded in memory. The exception to this is the Navigator, which needs root access, so doesn't run as a zygote and gets its libraries from the IFS.

In addition, to speed the launch of applications, the HTML5 apps in the prebuilt images are "minified". Minification makes the source code smaller by removing comments and white space, and possibly also shortening symbol names. The resulting code loads faster in the HMI. We recommend that you minify your HTML5 and JavaScript code for production, which you can do using any off-the-shelf minification tool.