{"id":68720,"date":"2014-06-27T10:41:49","date_gmt":"2014-06-27T08:41:49","guid":{"rendered":"http:\/\/onsoftware.en.softonic.com\/?p=68720"},"modified":"2025-07-02T00:37:13","modified_gmt":"2025-07-02T07:37:13","slug":"android-auto-simplified-android-for-your-car","status":"publish","type":"post","link":"https:\/\/cms-articles.softonic.io\/en\/android-auto-simplified-android-for-your-car\/","title":{"rendered":"Android Auto: Simplified Android for your car"},"content":{"rendered":"

There’s nothing really amazing about Android Auto<\/strong>. The idea is pretty basic – connect your Android phone to your car, and the Android Auto app will lock your phone and show a set of controls designed for use while driving. This includes phone calls, messaging, music, and connected car diagnostics.<\/p>\n

At Google I\/O 2014<\/a>, there were a few car makers showing off cars that supported the new Android Auto platform. Since I’m not big into cars, I only recognized the Honda Civic and Audi S3 that were being used to provide short demos. The ten minute demo showed the same features from the keynote, but when sitting inside a car, it’s a little more interesting.<\/p>\n

\"Android<\/p>\n

Touchscreen and in-car controls<\/h3>\n

The keynote showed an example of a driver using the touchscreen<\/strong> for Android Auto. But in the S3, it doesn’t support touchscreen, instead using the Audi MMI system. It doesn’t seem as intuitive as using a touchscreen, but Audi owners are probably used to the system. I was told that it’s up to the car manufacturer<\/strong> regarding what system will be used.<\/p>\n

Your phone displayed in the car<\/h3>\n

I decided to get the demo in the Audi S3<\/strong> because it’s a luxury car that I’ll probably never own. Getting in the car, an Android phone was connected to the car through USB<\/strong> and immediately the phone locked to show the Android Auto logo. Connection to the car is through the Android Auto app, meaning it’s not necessarily a native connection.<\/p>\n

\"Android<\/p>\n

The interface looks like Google Now<\/strong>. It can show relevant information like saved direction searches and appointment information. With voice recognition, you can search for locations, and the app is designed to give you the most important information like the operating hours of a restaurant. It won’t load information like the restaurant menu, however, because Android Auto is all about keeping your focus on driving.<\/p>\n

The in-car screen<\/strong> is a simplified interface with a bottom row of icons for actions. The supported features are the most obvious. Navigation through Google Maps<\/a>, calls and messages, and music are the most basic. Interestingly, the icons don’t necessarily apply to first party apps; it looks like you’ll be able to use any app<\/strong> that supports Android Auto. The option to choose apps is under different nested menus.<\/p>\n

\"Android<\/p>\n

Since the phone is connected to the car, any audio will play through the car’s audio system. With a lot of current cars supporting phone calls without headsets, it’s possible to chat or use voice recognition to send messages.<\/p>\n

The music apps shown were Spotify<\/a> and Google Play Music<\/a>. I did ask if locally stored files would be playable, and was told that local storage was supported<\/strong>. The Android Auto team doesn’t want you to have to worry if you don’t have a stable network connection, like in a parking garage.<\/p>\n

\"Android<\/p>\n

Calls through voice were demoed, but the feature isn’t really new and has been available for in-car systems for some time.<\/p>\n

Car diagnostics<\/h3>\n

The feature I think is most interesting is the diagnostics section<\/strong> that Android Auto hasn’t really shown off. Being able to know more about various diagnostics on screen will be great for drivers who usually don’t pay attention. How much information car makers will display is unknown, but enthusiasts will probably enjoy it.<\/p>\n

Still a lot unknown<\/h3>\n

The demo was shown by connecting the Android phone to the car through USB. Android Auto hasn’t explained the exact process of how the phone will connect to the car, other than that it will use the Android Auto app. It would make sense for the phone to connect wirelessly.<\/p>\n

My colleague\u00a0Lewis<\/a>, a car enthusiast, is also curious if Android Auto will be compatible with older cars, because he’s “not going to buy a new car just for Android Auto.”<\/p>\n

\"Android<\/p>\n

Android Auto<\/strong> could be a great platform. The support from car makers is a good sign, but the question now, is how can apps integrate into Android Auto and be useful?<\/p>\n

The first cars with Android Auto are expected before the end of the year, and the Android Auto SDK will be available for developers to design apps for the platform. But Android Auto will need some sort of legacy support to really be adopted.<\/p>\n

If you want more, check out my roundup of events and announcements from Google I\/O<\/a>.<\/strong><\/p>\n

Follow me on Twitter: @chrislikesrobot<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

There’s nothing really amazing about Android Auto. The idea is pretty basic – connect your Android phone to your car, and the Android Auto app will lock your phone and show a set of controls designed for use while driving. This includes phone calls, messaging, music, and connected car diagnostics. At Google I\/O 2014, there … Continue reading “Android Auto: Simplified Android for your car”<\/span><\/a><\/p>\n","protected":false},"author":2030,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wpcf-pageviews":0},"categories":[],"tags":[],"usertag":[],"vertical":[],"content-category":[],"class_list":["post-68720","post","type-post","status-publish","format-standard","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/68720","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/users\/2030"}],"replies":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/comments?post=68720"}],"version-history":[{"count":1,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/68720\/revisions"}],"predecessor-version":[{"id":330563,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/68720\/revisions\/330563"}],"wp:attachment":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/media?parent=68720"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/categories?post=68720"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/tags?post=68720"},{"taxonomy":"usertag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/usertag?post=68720"},{"taxonomy":"vertical","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/vertical?post=68720"},{"taxonomy":"content-category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/content-category?post=68720"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}