Downloaded 92 times
Uploaded byGodfrey Nolan
Android Auto
This document outlines an agenda for a Google Dev Fest on Android Auto. It includes an introductory demo of Android Auto capabilities, guidelines for setting up hardware and enabling apps, UI guidelines to minimize distraction, and a discussion of the future of connected cars. Developers can create apps that integrate with Android Auto to allow users hands-free access to messaging, media, and other apps while driving safely. The document provides resources for developers to get started with Android Auto.
More Related Content
![[MirrorLink Hackathon] Intro to the MirrorLink API, requirements & tools by E...](https://cdn.slidesharecdn.com/ss_thumbnails/workshoppresentationbyed-150525140220-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
Android Auto
- 1. Android Auto Google DevFest 5/9/15
- 2. Agenda • Intro andquick demo • Setting up your own hardware • Auto enabling your app • UI Guidelines • Rolling it out • Caveats • What does the future bring • Resources
- 3. Intro • Who, what,where, when and how • Replaces existing dashboard • Communicates via USB • 28 manufacturers signed up • Audio and Messaging API only • 2 dozen Auto apps in the app store • Hyundai 2015 models & Pioneer AVH car stereo
- 4.
- 5. Intro • Limited APIs– audio & messaging – but it will get better • Limited templates for safety reasons • Developer provides images, colors and strings • Extend existing apps • APIs, sample apps and simulators available • Driver responds to notifications • Text -> Voice -> Text
- 6. Intro - Demo •Download Android Auto API simulators extras using SDK Manager • adb install messaging-simulator.apk from extras folder • adb install media-browser-simulator.apk from extras folder • Download sample MessagingSerivceapp and install • http://developer.android.com/samples/MessagingService/index.html • adb install MessagingService.apk • Send message from MessageService app • View in Messaging Simulator
- 7.
- 8. Setting up yourown hardware
- 9. Setting up yourown hardware • Using Pioneer AVH-4100NEX car stereo • Parking brake bypass • 2 Amp, 12V DC to 120V AC transformer • Follow instructions https://www.youtube.com/watch?v=QntZ3A4bG4w • Connect brake bypass • Update Pioneer AVH firmware to 1.03 or above • Install Android Auto from Google Play onto Android 5.x phone • Connect Android phone using USB slot 2 • Accept all warnings etc. • Connect speakers, connect microphone
- 10. Auto Enabling yourApp • Provide Android Auto with messages so that car can read them out
- 11. Auto Enabling yourApp • Update NotificationBuilderwith CarExtenderto pass message to car
- 12. Auto Enabling yourApp • Add RemoteInput to allow car to reply to message
- 13. Auto Enabling yourApp • AndroidManifest.xml changes • New /res/xml/automotive_app_desc.xml file
- 14. UI Guidelines –Creative Vision • Glanceable and simple • Predictive, yet predictable • Connected • Naturally integrated
- 15. UI Guidelines -Minimizing driver distraction • Requirements • Fonts & Sizing • Text String Lengths • Contrast Ratio • Night vs Day modes • Imagery & Video • Advertising • Auto-Scrolling Text
- 16. UI Guidelines -Design Principles • Don’t port app into Android Auto • Focus on primary actions and content • Don’t include complicated flows • Keep choices to recent, frequent or favorite type choices • Complex actions occur on mobile app when car is stopped.
- 17. UI Guidelines -5 Discrete sections • Activity Bar and App Switching • Navigation Drawer • Overview Screen • App View and its menu (not yet) • Demand Layer
- 18. UI Guidelines -5 Discrete sections • Activity Bar and App Switching • Navigation Drawer • Overview Screen • App View and its menu (not yet) • Demand Layer
- 19. UI Guidelines -5 Discrete sections • Activity Bar and App Switching • Navigation Drawer • Overview Screen • App View and its menu (not yet) • Demand Layer
- 20. UI Guidelines -5 Discrete sections • Activity Bar and App Switching • Navigation Drawer • Overview Screen • App View and its menu (not yet) • Demand Layer
- 21. UI Guidelines -5 Discrete sections • Activity Bar and App Switching • Navigation Drawer • Overview Screen • App View and its menu (not yet) • Demand Layer
- 22. Getting it intothe Google Play • Upload to Google Play in the alpha channel for testing • Experience the joys of the new review process • Publish • Wait for the rest of the world to catch up
- 23. Caveats • Driver Distraction •Should be mostly voice activated • Simulator doesn’t support voice • NHTSA 2/12 guideline, 2 second glance, 12 second total interaction • Locked Screen • Any difficult interactions take place when car is parked • My favorites type transactions • Make the car experience better • Who pays for any recalls • More Fragmentation
- 24. Predicting the Future •MORE APIs – fingers crossed at Google I/O • Gamification, e.g. Facebook challenges • Cloud based apps and Mashups • OTA Dealer recalls • Huge impact on Detroit? • Connected cars • DSRC –Dedicated Short Range Communications • V2X and V2I • Autonomous cars
- 25.
- 26.