Home / ICT / Smartphone Integration (Report & Database)

Smartphone Integration (Report & Database)

Published: Dec 2011 | Published By: SBD

Product Synopsis

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:

  • Having a longer term vision for connected services
  • Adding value to the app ecosystem
  • 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

1. Executive summary
1.1 Introduction
1.2 SBD’s three-step approach to smartphone integration
1.2.1 Step 1 ~ Have a longer term vision for connected services
1.2.2 Step 2 ~ Adding value to the app ecosystem
1.2.3 Step 3 ~ Choosing solutions based on company-specific needs

2. Dock-based integration
2.1 Solution overview
2.2 Challenges ~ Legislation and business model
2.3 Points to consider

3. Proxy solutions
3.1 Solution overview
3.2 OEM app approach
3.3 Multi-app approach
3.4 Cloud integration and authentication

4. MirrorLink and RealVNC ~ Recent developments
4.1 MirrorLink ~ Recent developments
4.1.1 Certification process
4.1.2 Car-mode app
4.2 RealVNC and MirrorLink ~ Understanding the differences
4.3 Future outlook

5. Summary table


Fig. 1 The role of smartphones in enabling a seamless user experience
Fig. 2 Timeline ~ Challenges to the role of smartphones in the car
Fig. 3 Using standardised APIs to make apps platform agnostic
Fig. 4 Implementing SBD’s 3 step approach to smartphone integration ~ Examples
Fig. 5 Docking solutions in EU and the US
Fig. 6 US ~ States banning all forms of mobile phone usage for young drivers
Fig. 7 Smart Drive iPhone kit ~ Change in business model
Fig. 8 OEM app implementation options
Fig. 9 Multi-app approach ~ API-based differences
Fig. 10 Airbiquity’s cloud authentication platform
Fig. 11 Latest members to join the Car Connectivity Consortium
Fig. 12 Conformance testing process for certifying MirrorLink devices
Fig. 13 MirrorLink app certification process
Fig. 14 Car Mode application for MirrorLink; Video ~ Toyota IQ
Fig. 15 Phone vendor-specific Car Mode HMI on same in-car head unit
Fig. 16 RealVNC and MirrorLink ~ Implementation consequences
Fig. 17 RealVNC implementation across multiple platforms ~ Example
Fig. 18 Summary table

Choose License Type
Contact Information
24/7 Research Support
Phone: +1-855-455-8662
Get in Touch with us
join us on Facebook
Follow us on Twitter
Follow us on LinkedIn
Add us on Google +