Understanding Mobile Apps for Automotive Kerry Johnson, Senior Automotive Product Manager Confidential Information of QNX Software Systems Limited 2
PSA Bentley
In 2011
• 60+% of infotainment systems shipped QNX in automotive? • 9+ million world wide (5+ million in NA) • 40+% of all cars sold in US
Confidential Information of QNX Software Systems Limited 3
Automaker Primer What an app author needs to know about the automotive market in 10 minutes Confidential Information of QNX Software Systems Limited 4 The Lingo
• OEM = Automaker – GM, BMW, Audi, Toyota, Chrysler, etc • Tier1 = Module supplier – Delphi, Harman-Becker, Denso, Panasonic, Visteon, etc • Tier2 = Software/hardware supplier – QNX, Freescale, TI, Pandora, Red Bend, etc • RFI, RFQ, RFP – Request for info, quote, proposal • Head unit, center stack – Navigation hardware module • Infotainment – Information + entertainment + nav + telematics + hands-free Confidential Information of QNX Software Systems Limited 5 Infotainment and telematics examples • Audi MMI 3G • BMW ConnectedDrive • Chevy MyLink • GMC/Buick IntelliLink • OnStar • Toyota Entune • Toyota Touch&Go • Hyundai Blue Link • (MyFord Touch—not us!) Confidential Information of QNX Software Systems Limited 6 Consumer vs OEM lifecycle
Applications
Smartphones
Vehicle electronics
SOP Year 5 Year 10 Confidential Information of QNX Software Systems Limited 7 Development takes 3 years!?!
1. Lemons
2. Lawyers Confidential Information of QNX Software Systems Limited 8 Driver distraction Confidential Information of QNX Software Systems Limited 9
Cars: Where are they? Where are they going? Confidential Information of QNX Software Systems Limited 10 Head-units yesterday
• 1930: First commercial car radio • 1952: First FM radio • 1955: First ‘music-on-demand’ • 1963: First transistor radio • 1965: First eight-track • 1970: First cassette player • 1985: First CD player Confidential Information of QNX Software Systems Limited 11 Head units today
• Typical hardware – 32-bit CPU w/MMU: ARM (single, dual and quad core Cortex A8/A9 for mid- to high-end modules) – RAM & flash: 16/32MB (hands-free) to 256/512MB (infotainment)
• Infotainment system features – Hands-free calling – Speech recognition – Navigation system – Satellite + Internet radio – Mobile connectivity
Confidential Information of QNX Software Systems Limited 12 Head units tomorrow
Same features as today, but add: • Add (car-relevant) social networking
• Extend mobile connectivity – Import apps from phones – View apps running on phones – Share hybrid app between car and phone
• Run apps and app stores
• Connect to cloud-based services
Confidential Information of QNX Software Systems Limited 13 Why HTML5 for auto?
• Cross-platform – deploy apps on phones and car – extend by using mobile developers, tools, companies • Flexibility – flow deployment and architectures together as needed – brand same app on different cars with CSS • Time-to-market – leverage the ease-of-use of high-level language – program in rich application environment • Lifespan – get support for the lifecycle of the product – avoid vendor lock-in with standards Confidential Information of QNX Software Systems Limited 14
How can I build my app for the car? Confidential Information of QNX Software Systems Limited 15
Bringing CE into the car: Simple? Confidential Information of QNX Software Systems Limited 16 Bringing CE into the car: HARD!
• Nearly unlimited product liability and warranty
• 10+ year part and price availability
• Control of functionality
• Control over look and feel (depends on brand)
• Vehicle bus security
Confidential Information of QNX Software Systems Limited 17 Apps for auto
• 30 not 30,000
• Driver distraction
• OEM validation
Confidential Information of QNX Software Systems Limited 18 MirrorLink
VNC - screen content
cmd & ctrl
A2DP - audio
Confidential Information of QNX Software Systems Limited 19 MirrorLink pros and cons
• Pros – Exists today – Based on standards and well-known technology – Has qualified auto industry support
• Cons – Interface served up by phone; not necessarily ‘snappy’ – OEM-unique acceptance – No centralized ‘app store’ Confidential Information of QNX Software Systems Limited 20 Putting my app in the car today
• Working with an OEM? – Exposure, exposure, exposure – Automotive app store
• Working with the QNX CAR application platform? – Making the link between auto OEM and the applications – Leverage mobile investment – HTML5 SDK
Confidential Information of QNX Software Systems Limited 21 WebWorks for QNX CAR platform
• Adding APIs for car-specific features – Vehicle bus features: HVAC, body, electrical systems – Audio system
• Underlying HTML5 engine provides hardware accelerated graphics – Webkit-based transitions optimized to make use of the NVIDIA Tegra GPU Confidential Information of RippleRipple emulatorfor QNX CAR for QNX CAR platform QNX Software Systems Limited 22 Confidential Information of QNX Software Systems Limited 23
Driver distraction for the uninitiated Confidential Information of QNX Software Systems Limited 24 Distraction avoidance guidelines
High-level extraction from various guidelines – AAM, USDOT, SAE, ITU-T
1. Minimize off-road glances – Design app so only need glances of 2 seconds or less at a time – Minimize visual information in driver’s field of view • Remove clutter, animations, eye-candy, embellishments, etc. – Intelligent use of ASR/TTS Confidential Information of QNX Software Systems Limited 25 Distraction avoidance guidelines
2. Minimize total task duration – Don’t make any one task (from action to achieved) take longer than 15 seconds – Interruptions not counted – Does not imply you can have eyes off road for 15 seconds…
3. Make applications interruptible – Drivers should be able to pause, resume interaction – Assume 2 second ‘chunkability’ – If understanding how or where to resume takes >2 seconds, app will be unusable
Confidential Information of QNX Software Systems Limited 26 Distraction avoidance guidelines
4. Make applications predictable – Easy to anticipate application behavior – Results easily understood – Bad example: shifting menus
5. Make applications ignorable – Non-immersive user interfaces – Limit manual input required – Bad example: VR system with timeout on no response Confidential Information of QNX Software Systems Limited 27
Putting my app in the car tomorrow
27 Confidential Information of QNX Software Systems Limited 28 Crystal ball
• Don’t expect in-car systems to disappear – Rear seat category will be phased out – In-car systems broader adoption
• OEMs slowly opening up – App sandboxes – Automotive SDKs
• Within North America, expect to see – Streamlined module validation – Streamlined app certification
28 © 2012 QNX Software Systems Limited. QNX, QNX CAR, NEUTRINO, MOMENTICS, AVIAGE and other product names are or may be registered trademarks and/or trademarks of QNX Software Systems Limited (QSSL) or its licensors in Canada, the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of QSSL as of the date of Any questions? this presentation. Because QSS must respond to changing market conditions, it should not be interpreted to be a commitment on the part of QSSL, and QSSL cannot guarantee the accuracy of any information provided after the date of this presentation. QSSL MAKES NO WARRANTIES, REPRESENTATIONS OR CONDITIONS EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Kerry Johnson [email protected]
qnx.com/careers