using qt for automotive infotainment development

Post on 12-May-2015

1.737 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

DESCRIPTION

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. http://qt.nokia.com/developer/learning/elearning

TRANSCRIPT

Qt in automotiveJens Cederhage, Cybercom Group 10/16/2009

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

INTRODUCTION

Who am I and why am I here?and why am I here?

CybercomWhy are we in this business?

� Upgrading software

� Mobile content

� Mobile Internet

� TrackID

� DM/Fota

sonyericsson.com

� saab.com

�PlayNow™

� Purchasing� User interface

� PIM; Phonebook etc

� Infotainment

� SIM Card technologies

�Embedded HW and SW

� Crypto communication

� Wireless security

� IT forensics

� e-ID

� Roll outs

� Audits

� Transactions

� Revenue

assurance

� Roaming

TRENDS

4

What will happen?

5

In order to fill the car with the current and tomorrows trends the car infotainment should be built like a smart phone.

Problems

6

• Development cycle = long• Life cycle = long• SW cost = “high”• UI = “poor” experience• Feature set = low• Processes = static

• Development cycle = short• Life cycle = short• SW cost = “low”• UI = “good” experience• Feature set = high• Processes = agile

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• Its all about user experience

• Use already existing software solutions

7

Wireless infotainment platform – a Qt solution

• RSS feeds

• Widget support

• Media player

• Audio books

• Browser

8

• Browser

• Navigation

• Web radio

Examples – wireless infotainment platform

9

More examples – wireless infotainment platform

10

top related