Workflow Demonstration with Kanzi Studio and Kanzi Connect

Kanzi Simulator screenshot_1920

This end-to-end demonstration showcases the use of Kanzi Connect as both a development tool and a means to integrate multiple devices into a seamless user experience. We walk through the drag-and-drop ease with which an automotive UI can be modified and updated with Kanzi Studio, and we show how Kanzi Connect integrates data across the instrument cluster and IVI system. Finally, we demonstrate the benefits to the UI designer of Kanzi Connect as a data simulation tool during the development process.


 In the setup, we have a laptop running the Kanzi Studio project, a cluster running on commercial target hardware based on Linux, an Android-based IVI application, and an Android phone. What ties all these together is Kanzi Connect, which allows us to share any data and any service across all the displays. For example, if we change the song that’s playing on the phone, we can see the song changing across all the devices. Similarly, when we turn on the gyroscope on the phone and wiggle the phone, we can see the data from the gyroscope reflected across all of the devices in real time. And a new feature of Kanzi Connect is the Simulator. Shown here running in a browser, it allows us to provide simulated data into the design process.

To explore how easy it is to make design changes, bind elements to data sources, and deploy them to target hardware, we start with a blank page in the instrument cluster project. We drag three premade widgets onto the page: a speedometer, a colored sphere, and a media player. To show the cover art for the track that’s playing, we create a biding between the data source and the property in the media player simply by dragging and dropping. Now the cover art is shown across all the displays, even including the Kanzi Studio project. The second thing we want to change is the color of the sphere, and we want to tie it to the drive mode. The properties of the sphere (0, 1, and 2) relate to green, blue, and red, and we want to map those colors to eco mode, normal mode, and sport mode. Again, we simply drag the data source onto the property to create the binding. Now when we use the Simulator to change the drive mode from eco to normal to sport, the color of the sphere changes accordingly.

The final step is to export this project and move it to target hardware. No compiling is required: we export the binary file directly from Kanzi Studio, and drag it across to the hardware platform. When we restart the application on target we can see the live project, with the media player, drive mode sphere, and speedometer now implemented.

That’s how easy it is to design, iterate, test with simulated data, and deploy to target hardware with Kanzi Studio and Kanzi Connect.

Learn more about Kanzi workflow. To request a trial license for Kanzi, please visit

The Karma Revero GT and GTS case study: building a unique user experience