Why should we bundle our UX apps?

Reduce hundreds of HTTP requests and improve performance by bundling web resources into single production files using tri-vulcanize for Polymer 1 or tri-bundler for Polymer 3 applications.

A typical IBM® Maximo® Real Estate and Facilities UX app might initially load hundreds of resource files which translate to the same number of HTTP requests from the server to the browser. This remains true in successive requests of these resources even if they are already cached by the browser. The browser still makes the same number of HTTP requests to the server, then waits for the server response to either load it from the cache or from the latest version from the server. This high number of HTTP requests can be costly and can negatively impact the performance of your UX app.

One way to cut down this cost is to concatenate or bundle these web resources into a single production file. For Polymer 1, we used the tri-vulcanize tool. But for Polymer 3, we're using the tri-bundler tool.

Note: The tri-bundler tool is designed specifically for Polymer 3. To be clear, our UX framework supports both Polymer 1 and Polymer 3 UX apps. Both types of UX apps can coexist together in the same environment. But if you're interested in Converting UX to polymer 3 your own custom UX apps from Polymer 1 to Polymer 3, see the Converting UX to polymer 3 tool. Be aware that this tool is not officially supported at this time.