Open Source Automotive Development
Upcoming SlideShare
Loading in...5

Open Source Automotive Development



OpenCar covers OS development for a new market: automotive apps. In-car apps are poised to explode for open source developers. The market is transforming from an inefficient, proprietary model to an ...

OpenCar covers OS development for a new market: automotive apps. In-car apps are poised to explode for open source developers. The market is transforming from an inefficient, proprietary model to an HTML5-based “app store” model. To enter and participate in this new target category, developers need access to automakers, automotive systems, and knowledge of industry standards and platforms.



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Open Source Automotive Development Open Source Automotive Development Presentation Transcript

  • OSCon 2013 July 25, 2013
  • Past - Present 2  
  • Going Forward 3   View slide
  • Motivations 4   View slide
  • Developer Motivation  Large  Addressable   Market Developer  Interest Choice Consumer  interest
  • Developer Motivation •  New vehicle factory-installed connected car penetration: 60% by 2017 •  Installed base forecast: 350mm+ subs in 2017 (ABI) •  Uptake will soar in the next 12-18 months, with Europe and China launches •  Government telematics mandates accelerate adoption (Europe, Russia and Brazil) 0   50   100   150   200   250   300   350   400   2008   2009   2010   2011   2012   2013   2014   2015   2016   2017   Global  AFermarket  Subscribers  (Millions)   Global  OEM  Subscribers  (Millions)   0.00%   10.00%   20.00%   30.00%   40.00%   50.00%   60.00%   70.00%   2008   2009   2010   2011   2012   2013   2014   2015   2016   2017   Connected  Car  PenetraOon  into  Vehicles(%)  
  • Learning Curve •  Devices / Sensors: Engine, Drivetrain, Chassis, Electrical, GPS, Accelerometer, Windows, Locks, Seats, Doors, Mirrors, Heater, A/C, Fan, Defrost, Seat Warmer, Climate Zones. •  Onboard Entertainment: AM/FM/CD/XM/USB/SD/AUX, Storage Media. Analog and Digital sources. Bluetooth (A2DP/AVRCP). iPod support. •  Control: Commander, Bezel Buttons, Steering Wheel. •  Host Services: Remote Voice Commands, Local Voice Commands, Text-to- Speech, On-board OR Off-board Telephony, Bluetooth, Specialized Host Connectivity Options (Bluetooth/USB/WiFi/NFC) •  Host Platform Support Differences: Device Protocols, Media Player Interfaces, Internet Services, Persistence and Security, Telematics Management, Update Installer, 3rd Party Native App Support 7  
  • Current Engagement Model: Broken Develop   InteresOng  App Strike  OEM   Deal Customize  HMI   for  target   vehicle Test/Validate   and  Deliver  App Localize  App  for   Each  Global   Market New  Model,   New  HMI App  Revision,   New  HMI Two designers take 6-8 weeks to design a new app Three developers take 8-12 weeks to develop, test, & release Additional cars, functionality, testing 3-4 updates per year to keep app fresh and competitive The “Million Dollar App” New  OEM  Deal,   Start  Again
  • Varying Degrees of “Open” •  Published APIs to automaker’s proprietary systems: –  BMW ConnectedDrive –  Ford –  GM –  OpenCar ( •  Full Systems –  GenIVI open source initiative –  Wind River, Monta Vista, XSe –  QNX
  • OS Vendor Decision Criteria •  Established relationships •  Automotive development expertise •  Maintenance and support expertise •  Automotive infotainment development expertise •  Kernel / Driver development expertise •  Current platform module support –  USB, Ethernet, SPI, CAN, GPU, etc •  Total cost, including license if applicable •  Ability to meet development schedule •  “Risk factors” –  Resource stability –  Resource scalability –  Confidentiality matters 10  
  • Different SDKs, Different Business Goals Goal Ford GM OpenCar Expand application catalog using 3rd party developers ✔ ✔ ✔ Free publicity and brand extension via software community ✔ ✔ ✔ Reduce overall development costs ✔ ✔ ✔ “Lock-In” developers to single OEM brand ✔ ✔   Leverage and capitalize on smartphone consumer focus / popularity ✔   ✔ Code portability across models (within a brand) ✔ ✔ ✔ Code portability across operating environments (head units, OS, etc) ✔ ✔ Code portability across OEMs ✔
  • 2011 (Non-China) Light Vehicle Sales 12  
  • User Experience and Design for Cars
  • User Experience Principles •  Anticipate user’s needs •  Be consistent •  Provide cues and system feedback •  Offer predictable system behavior •  Avoid superfluous features •  Make the experience snappy and responsive •  Empathize with the user
  • Driver Experience Where User Experience meets Automotive Safety
  • Safety
  • Safety 17  
  • Safety Principles •  Do not distract or visually entertain the driver •  Complete tasks in short, sequential glances •  All text and icons are legible •  Ample contrast in all lighting situations •  Interaction sequences are interruptible and resumable •  Interaction pace is controlled by the driver •  System feedback is timely and clear •  Driver does not need to keep his/her eyes on the display
  • 20  
  • 21  
  • 22  
  • Platform Drill-Down
  • Development Architecture The Car as a Platform •  CAN, LIN busses •  OBD II •  Other feeds: GPS, Telephony, Audio, Accessory systems •  Inputs: HMI Voice, Touch •  Connection to Cloud services
  • HTML5 in Cars Critical Component •  Embedded Browser in IVI, eg WebKit OpenCar Platform and SDK •  Supporting UI Layer to screens and HMI controls and microphones •  Runs on IVI or Smartphone OS •  Manages APIs and Services to Car and Cloud •  OS X-ready development environment provides an API solution implemented on a Linux platform against open-source host services
  • Inside Track Developer Support Site 32   •  Comprehensive API Documentation •  Designer’s Guide: UX style best practices for safety compliance (NHTSA, AAM, JAMA, ESoP specific templates). •  Developer’s Guide: “How to” configure, code, test, and deploy OpenCar applications. •  Resources, FAQs, Release Notes. •  Upcoming additions: Support forums and developer community, Publishing and deployment guidelines, Developer training programs, hackathons, and more.