Using Qt for Automotive Infotainment Development


Published on

The continuously growing trend of “always connected” is starting to influence the automotive industry. People are becoming more and more used to consuming both content and services wherever they are, which also applies when driving. Today a driver's only choice is to consume the services and content trough his phone because the automotive industry has no chance to keep up with the rapid development cycles of the ND and CE industry. By using Qt, in a future infotainment system, the OEMs will be able to change this. A Qt based system enables them to piggy back on the development already done in other industries giving them shorter time to market, lower cost, more flexibility and a huge step towards a better user experience.

Presentation by Jens Cederhage held during Qt Developer Days 2009.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Using Qt for Automotive Infotainment Development

  1. 1. Qt in automotive 10/16/2009 Jens Cederhage, Cybercom Group
  2. 2. INTRODUCTION • INTRODUCTION • AUTOMOTIVE - INFOTAINMENT – Trends – Problems – Criteria's for a successful solution • Qt – Why use Qt? – What have we done using Qt? • Q&A 1
  3. 3. INTRODUCTION Who am I and why am I here?
  4. 4. Cybercom Why are we in this business? PlayNow™ Purchasing Upgrading software User interface Mobile content PIM; Phonebook etc Infotainment Mobile Internet SIM Card technologies TrackID Embedded HW and SW DM/Fota Transactions Roll outs Revenue Audits assurance Roaming Crypto communication Wireless security IT forensics e-ID
  5. 5. TRENDS 4
  6. 6. What will happen? In order to fill the car with the current and tomorrows trends the car infotainment should be built like a smart phone. 5
  7. 7. Problems • Development cycle = long • Development cycle = short • Life cycle = long • Life cycle = short • SW cost = “high” • SW cost = “low” • UI = “poor” experience • UI = “good” experience • Feature set = low • Feature set = high • Processes = static • Processes = agile 6
  8. 8. What have we done to address this? Criterias • More flexibility towards HW design • More flexible SW design • HMI separated from application functionality • Its all about user experience • Use already existing software solutions 7
  9. 9. Wireless infotainment platform – a Qt solution • RSS feeds • Widget support • Media player • Audio books • Browser • Navigation • Web radio 8
  10. 10. Examples – wireless infotainment platform 9
  11. 11. More examples – wireless infotainment platform 10