Along with news about Android L and Android Wear, Google also announced a new vehicle focused initiative called Android Auto at this year's Google IO. Android Auto is Google's take on an in-car mobile experience and much like Apple's CarPlay it hopes to provide a seamless and unified experience across many different vehicles from many different manufacturers.

Google Auto starts by extending the interfaces that Android users are familiar with. It uses the same card based design and colorful backgrounds as Google Now, and it functions in a similar fashion with cards that display information about travel routes, music playback, and other relevant information. Android Auto works by connecting to the user's smartphone or tablet and translating all the content on that into a simpler and more navigable interface for a vehicle. The Android Auto system is also designed to be functional with only the use of voice controls which will hopefully reduce the number of car accidents that occur because a driver is using their cell phone without paying attention to their driving.

Android Auto has three main points of focus that Google feels are essential to providing the best in-car experience for the user. The first is a fairly obvious necessity for an in-car operating system, navigation support. By using Google Maps and Google's navigation features the Android Auto system acts as a hands-free GPS. The user can simply tell Google Now what destination they would like to navigate to and it will bring up a card with traffic info and an estimated travel time. The user can then confirm they wish to begin navigation and the map interface will open with driving directions spoken over the car's speaker system and a visual map displayed on the screen.

Communication is the second main focus of Android Auto. People are becoming increasingly connected and are constantly bombarded with phone calls, text messages, etc. Android Auto wants to make managing this constant communication safer for users by letting the user keep their hands on the wheel and eyes on the road rather than fiddling with their smartphone. Because Android Auto works by running off of the user's phone it can display notifications for texts, calls, and other messages right on the vehicle's built-in display alongside all the other cards for navigation and music. The user can use Google Now to dictate a message using their voice and then send it without ever having to pick up their phone. They can also make phone calls and speak aloud without having to use one of their hands to hold their phone up to their ear. These features are great because they serve a dual purpose of simply being more convenient for the user, but also letting people drive safely while still being able to use their mobile device.

The third point of focus is on music playback and streaming. Many people listen to music over the speakers in their vehicle and Google wants to make it easy for people to get to the songs they want to hear and to have access to all their music stored on their device as well as across multiple streaming platforms. As you can see above, Android Auto features a very simple interface for music playback with big buttons that are easy to press. Like all the other features in Android Auto, the user can also control their music playback via voice control which makes navigating to a specific song as simple as asking Google Now to play that track. 

Google has also been working with major music streaming companies to get apps ready for Android Auto upon launch. Users will have access to all their music on streaming services like Pandora and Spotify in addition to all the music they have stored locally on their smartphone or tablet.

To ensure Android Auto is an ever evolving and improving experience for users, Google is making an Android Auto SDK available for developers so they can modify their apps to be functional and well integrated on in-car displays running this new extension of Android. Google has stated that the Android Auto experience will be available to users alongside the public Android L release later this year and that over 25 automobile manufacturers have signed up to ship cars with Android Auto support in the near future. More information on the list of manufacturers that plan to include Android Auto in their vehicles can be found on the Open Automotive Alliance website which is the home for all companies committed to using Android in automobiles.

POST A COMMENT

18 Comments

View All Comments

  • acton11 - Thursday, June 26, 2014 - link

    Android has had the ability to do offline speech recognition since Jelly Bean. Reply
  • SleepyFE - Thursday, June 26, 2014 - link

    Thanks for the info. I got android 4.0.3 so i still have to go online.
    In that case: FINALLY WE WILL GET OUR VERY OWN KITT!! GOTTA LOVE IT!!
    Reply
  • piiman - Sunday, June 29, 2014 - link

    "For voice recognition you have to be connected to Google's servers."

    No you don't
    You speak into phone and them it connects, translates the command and then disconnects. Its not a data consuming thing. As for the button not being safe because you have to look..........give me a break! It takes all of 1/2 second or less to glance at the screen. I'm sure you take your eyes off the road for that amount of time many times during a drive.
    Reply
  • acton11 - Thursday, June 26, 2014 - link

    Also, as Ortanon said, the car maker will decide what physical buttons will be available. I hope some of them read your comment and do supplement the touch screen with physical buttons. I'd definitely like to have the option to use the touchscreen, voice control or physical buttons depending on what I'm doing.

    For example, in my current car, my steering wheel has physical buttons for volume control, music player control (pause, skip, fast forward, rewind), phone control (answer, hangup, ignore). The dash also has other physical buttons that supplement the screen controls. I hope/assume when the nav/audio/car control system is replaced with this Android based system, they'd keep/enhance the physical controls.
    Reply
  • SleepyFE - Thursday, June 26, 2014 - link

    Glad we're on the same page. Safety first. Then fancy features. Reply
  • piiman - Sunday, June 29, 2014 - link

    LOL nice to see you have no idea how it works. It only connects to a server and passes data when it is given a command. It doesn't stay live the entire time. You would use VERY little data. Reply
  • Daniel Egger - Sunday, June 29, 2014 - link

    There's no contradiction whatsoever. For voice recognition you'll need a live connection to one of Googles' servers. Period. If you had any idea of TCP/IP then you'd also know that it might even be more (data) efficient to keep a TCP socket alive for a long time rather then reestablishing for every voice command if there more than a few dictations per day. And even "VERY little" amounts of data might cost a lot of money if you're travelling across the border as can be quite common in Europe -- not that any ignorant US people would actually care.

    I also don't see why I would want to take such a huge step backwards as I do have nice physical controls in both of my cars and I have voice control if I wanted to (no, I usually don't because using voice control the system is not capable of supplying educated guesses and autocompletion) -- completely offline.
    Reply
  • Oooskar - Monday, June 30, 2014 - link

    It's a shame that it has been made this easy to call handsfree in a car. I read many scientifical reports which concluded that it didn't matter whether someone was holding their phone or calling handsfree, but keeping the conversation going was distracting (and because of that, dangerous). I hope governments will soon take notice and warn drivers for the real danger in calling while driving. Reply

Log in

Don't have an account? Sign up now