Asia: +65-6223-2436
Int'l: +1-860-674-8796
US: +1-866-353-3335
  • Japanese
  • Korean
  • Chinese
Cover Image

Connected Car: A status update on in-car smartphone integration

  • Published:
  • 38 Pages
  • SBD


The role of smartphones extends beyond in-car use to applications such as intelligent pre-trip route planning and last mile pedestrian navigation. A number of OEMs are investigating options to enable a seamless experience for customers between their connected world outside the car and the in-car environment.

With a wide range of solutions being developed in the automotive industry to safely integrate the functionalities of smartphones inside the car, how should you proceed? SBD's latest report 'A status update on in-car smartphone integration' clarifies and analyses the various approaches being proposed for smartphone integration.

This report recommends a three-step approach to smartphone integration:

  • 1. Having a longer term vision for connected services
  • 2. Adding value to the app ecosystem
  • 3. Choosing solutions based on company-specific needs

This report is complemented by an smartphone database containing all the OEM solutions for smartphone integration available in Europe and the USA.


This report will help you:

  • Understand how smartphone integration can be a part of your longer term vision and company-specific needs
  • Smoothly transition between smartphones, browser apps and native apps to provide a consistent end user experience
  • Build a successful solution and maintain the balance of creating apps in house and handing over control to consortiums
  • Learn about the recent developments and differences between MirrorLink and RealVNC screen duplication solutions

Table of Contents

1. summary1. Executive summary

  • 1.1 Introduction1.1 Introduction
  • 1.2 three1.2 SBD's three--step approach to smartphone integrationintegration
    • 1.2.1 Step 1 ~ Have a longer term vision for connected servicesconnected services
    • 1.2.2 Step 2 ~ Adding value to the app ecosystemecosystem
    • 1.2.3 Step 3 ~ Choosing solutions based on companycompany--specific needsspecific needs

2. Dock2. Dock--based integrationbased integration

  • 2.1 overview2.1 Solution overview
  • 2.2 model2.2 Challenges ~ Legislation and business model
  • 2.3 consider2.3 Points to consider

3. solutions3. Proxy solutions

  • 3.1 overview3.1 Solution overview
  • 3.2 approach3.2 OEM app approach
  • 3.3 Multi3.3 Multi--app approachapp approach
  • 3.4 authentication3.4 Cloud integration and authentication

4. developments4. MirrorLink and RealVNC ~ Recent developments

  • 4.1 developments4.1 MirrorLink ~ Recent developments
    • 4.1.1 process4.1.1 Certification process
    • 4.1.2 Car4.1.2 Car--mode appmode app
  • 4.2 RealVNC and MirrorLink ~ Understanding the differencesdifferences
  • 4.3 outlook4.3 Future outlook

5. table5. Summary table


  • Fig. 1 The role of smartphones in enabling a seamless user experienceuser experience
  • Fig. 2Fig. 2 Timeline ~ Challenges to the role of smartphones in carin the car
  • Fig. 3Fig. 3 Using standardised APIs to make apps platform agnosticagnostic
  • Fig. 4Fig. 4 Implementing SBD's 3 step approach to smartphone Examplessmartphone integration ~ Examples
  • Fig. 5Fig. 5 Docking USDocking solutions in EU and the US
  • Fig. 6Fig. 6 US ~ States banning all forms of mobile phone usage driversusage for young drivers
  • Fig. 7Fig. 7 Smart Drive iPhone kit ~ Change in business modelmodel
  • Fig. 8Fig. 8 OEM optionsOEM app implementation options
  • Fig. 9Fig. 9 MultiMulti--app APIapp approach ~ API--based differencesbased differences
  • Fig. 10Fig. 10 Airbiquity's platformAirbiquity's cloud authentication platform
  • Fig. 11Fig. 11 Latest members to join the Car Connectivity ConsortiumConsortium
  • Fig. 12Fig. 12 Conformance testing process for certifying MirrorLink devicesMirrorLink devices
  • Fig. 13Fig. 13 MirrorLink processMirrorLink app certification process
  • Fig. 14Fig. 14 Car Mode application for MirrorLink; Video ~ Toyota IQToyota IQ
  • Fig. 15Fig. 15 Phone vendorPhone vendor--specific inspecific Car Mode HMI on same in--car unitcar head unit
  • Fig. 16 RealVNC and MirrorLink ~ Implementation consequencesconsequences
  • Fig. 17Fig. 17 RealVNC implementation across multiple platforms Exampleplatforms ~ Example
  • Fig. tableFig. 18 Summary table
Show More