Qlik Sense mashups performance comparison using JavaScript and Angular

Mashups are an excellent way to show your data in a friendly web interface using Qlik Sense and as for every application on the web, performance matters. We at Sense Templates care about performance, so we made tests with the mashup API provided by Qlik with different mashup development techniques.

Mashup on the left in the image below – Using pure JavaScript with app.getObject() by demand, checking if an object has already been rendered earlier. All HTML used is on a single file, for both pages (page 1 and page 2).

Mashup on the right in the image below – Using Angular, calling app.getObject() by each controller. Since Angular changes the DOM (Document Object Model) content for each page change, all objects must be rendered again.

For consideration: Each mashup has 21 objects inside it and only 2 functional pages. Both tests were in Chrome.

The result is a more performatic navigation on a single page application using pure JavaScript, as we can see on the animation below.

Using pure Javascript with a single HTML makes the navigation faster, but it can be worse for maintenance on big projects. On the other had, using multiple HTML files with the Angular way can be pretty straightforward for development purposes, but not so fast for the end user as the pure JS/Single HTML option.

There is nothing wrong choosing one or another method, as long as it fits into the needs of your project. It is important to remember that we need to see our web interface like if we were the users, and they must have a pleasent experience in the end.

Leave a Reply

Your email address will not be published.