Connected Vehicle

First look of the Android-based UI from Google’s Open Automotive Alliance(OAA) finally revealed

Published: May 25, 2014


Google and NVIDIA announced partnership with GM, Honda, Audi, and Hyundai in forming the Open Automotive Alliance earlier this year at Consumer Electronics Show(CES). The initial announcement was predictably sparse on details, noting only the initiative’s core principles, and the goal of bringing Android to cars. After hearing approximately almost about the effort since then, the first look at Google’s vision for Android in the Car, referred to internally as Gearhead is revealed by Android Police.

Android in the Car: Is it finally coming?

Android in the Car (anticipated name due to unavailability of any official name), in its current state anyway, doesn’t look exactly like a science fiction fantasy, but it’s clear that a lot of thought is being given to functionality that’s actually helpful in the car, based around the kinds of things people do in their car, with Google’s special Search sauce applied liberally.

According to the sources, Android in the Car’s basic interface will center around four distinct spaces – navigation, music, telephony, and search. Although the detailed description of each interface is not available but we can atlleast expect how the music interface will likely look. This rumor gets a confidence level of 7/10. People at Android are pretty confident that Google’s Android in the Car interface will be functionally close to what we’ll look at today, though the actual interface could change drastically.

One question that still remains unanswered is whether it will allow the integration of 3rd party apps or will be reliant on OEM-run app store

Here is how the music interface will look like.

Voice-enabled Messaging

Sending a message can be accomplished through voice commands, where the user would say “send a message,” or “send a message to [contact name].” This would trigger Google’s usual back-and-forth where the message is dictated, confirmed, and sent.

A current design pattern with Google’s voice commands, the blue color indicates a time when Google is talking to the user. During these times, Google is clarifying with the user what information they want to use – in this example, which contact the user wants to message, and what that message should say. Once that’s cleared up, the message can be sent.

Hey and it doesn’t show the user his or her message before sending. That is what Google is for. It will read out the message for you and send it following your approval.


Users can enter a dialer interface that would allow them to select a frequent contact or dial a number, but users can also trigger a call using their voice, simply saying “Ok Google, call [contact name]” just like in Google’s mobile Search app. Presumably, the user’s phone would be connected to the car system via Bluetooth, which is where the call would actually take place.

Comments from Telematics Wire

Although the illustrations shown in the ARTICLE is not the final look but it is believed that the ultimate version will have similar features, if not more. Moreover, the previews in this articles are not fresh, may be 3-4 months older. We are sure that these User Interfaces(UIs) could have already achieved much upgradation as on date. By the time, the so called Android in the Car rolls out in the market, it will witness a substantial amount of refinement.

Needless to say, such release from Android is evidance for the fact that soon we are going to see the much-awaited Google’s dream of ‘Android in the Car’ coming true.

It is good to see how a Internet search company seems to be taking so much interest in automotive space.

Source: Android




Related Articles