Android Auto was unveiled this morning at Google I/O, Google's annual developer conference, with the announcement providing several clues about the direction that auto manufacturers will be going with the technology. In-car technologies will never be the same.
The driver's Android device, typically a smartphone, will be the heart and soul of how Android Auto works. Once the device is connected the phone will "cast" to the vehicle's in-dash screen. Android Auto is designed to work seamlessly with the vehicle's dials, buttons, and touchscreen.
Making the driver's mobile device the brains of the system has several important implications for in-car technologies moving forward:
- The product development lifecycle for in-car software will no longer be tied to the product development lifecycle of the car itself, which can be as long as 5 years. In-car technologies will no longer be outdated as soon as cars roll off the lot.
- The in-car experience will be as personalized as the mobile experience, as Android Auto will have access to just about anything that is already on the driver's device.
The presentation was light on detail but a live demo showed off key features including music, communication, navigation, and voice recognition. The SDK, which allows the developer community to create Android Auto apps, will be available soon with functionality initially limited to music and communication. Expect to see Android Auto enabled vehicles to show up on dealership lots this year.
The Open Auto Alliance, formed earlier this year to collaboratively create Android Auto, has expanded significantly to include almost 30 auto manufacturers and a group of technology partners, including Google.
It's fair to say that many are seeing the connected car as a key component of the Internet of Things (it's no coincidence that Google sandwiched Android Auto between announcements for wearables and televisions). With Google's Android Auto and Apple's CarPlay both officially in the mix, I can't wait to see what happens.