From 8662c04fd70ac25a8081b42b6850dab925c3c774 Mon Sep 17 00:00:00 2001
From: Luan Nguyen
- Important: The criteria listed in this page apply to your app's user interface - and behavior when running on devices connected to an Android Auto screen. Apps must meet these + Important: The criteria listed in this page apply to your app's user interface + and behavior when running on devices connected to an Android Auto screen. Apps must meet these criteria to qualify as an Android Auto app on Google Play.
@@ -94,7 +94,7 @@ page.image=/distribute/images/gp-auto-quality.png- App elements do not display any images on the Auto screen. Exceptions include: app may display + App elements do not display any images on the Auto screen. Exceptions include: app may display a single static image for - content context in the background of the consumption screen, such as album art, and app may + content context in the background of the consumption screen, such as album art, and app may display icons in the content navigation drawer.
+ App never presents any form of visual information (notifications, toasts, video, images, + advertising, etc.) on the phone screen while the app is active in Android Auto. +
++ App supports day mode, which renders dark text and controls on a light background. + (Learn How) +
+- App supports night mode, rendering light text and controls on a dark background. + App supports night mode, which renders light text and controls on a dark background. + (Learn How)
+ App provides white icon sets that the system colorizes to provide automatic + contrast compensation. + (Learn How) +
++ App provides colors that the system can optimize for easy in-vehicle readability. + (Learn How) +
++ App loads in no more than 10 seconds. +
++ Auto app functionality works as expected or described in the app's Google Play Store listing. +
++ Any app button which is non-functional or disabled must be grayed out. +
+App has no more than four primary actions plus one optional action overflow toggle (or five if - no action overflow is used). For more information, see details on the media control card in the - Android Auto UX Guidelines - for Media Applications. + no action overflow is used). + (Learn How)
- App has no more than four optional secondary actions plus one action overflow toggle. For more - information, see details on the media control card in the - Android Auto UX Guidelines - for Media Applications. + App has no more than four optional secondary actions plus one action overflow toggle. + (Learn How)
Important: Due to this restriction, you should not use your production APK - for Auto support prototyping. + for Auto support prototyping.
diff --git a/docs/html/distribute/googleplay/auto.jd b/docs/html/distribute/googleplay/auto.jd new file mode 100644 index 0000000..af24a54 --- /dev/null +++ b/docs/html/distribute/googleplay/auto.jd @@ -0,0 +1,237 @@ +page.title=Distributing to Android Auto +page.image=/design/auto/images/auto-overview.png +meta.tags="auto", "publish", "quality" +page.tags="auto", "publish", "googleplay" +page.metaDescription=Distribute your apps and content to Android Auto. + +@jd:body + ++ If you've got a great app, Android Auto and Google Play can help you + bring it to users right in their vehicles. You can + extend your new or existing apps for Auto and then publish them using familiar + tools and processes in Google Play. +
+ ++ To get started, review the sections in this document to learn how to + distribute your Auto apps to users through Google Play. Be sure to read + Auto App Quality + for information on the usability, quality, and safety-related guidelines that your apps should + meet. When your app is ready, you can accept the terms in the Developer Console and upload your + APK for review. +
+ ++ Google Play lets you deliver apps for use in vehicles. You can develop and publish using your + existing Developer Console account and your current distribution and pricing settings. It's easy + to participate — the sections below outline the process. +
+ +
++ To prepare for a successful launch on Android Auto, start by reviewing the + guidelines for creating great experiences on Auto. See the Android Auto design guidelines for ideas + on extending your app for Auto and details on design and usability. +
+ ++ As you get started designing your Auto experience, make sure to read and + understand the quality criteria for Auto apps. Only apps that are usable on Auto + will be designated as Auto apps on Google Play — your apps can participate + if they meet a set of basic quality criteria. See + Auto + App Quality for details. +
+ ++ A great app for Auto is designed for vehicle use and takes advantage of the + capabilities of Android Auto. The app offers a high-quality experience while the user is on the + go such as providing playback for audio content or accessing messages. +
+ ++ As you consider your Auto app, review the developer documentation and + usability guidelines and plan on supporting them to the greatest extent + possible. Make sure to design a great experience and adhere to our guidelines for preventing + driver distraction. +
+ ++ You must deliver your Auto experience as part of your existing app for phones, tablets, and other + devices, using the same package name and store listing. +
+ ++ Your Auto apps should be designed to perform well, look great in the car, + and offer the best user experience possible. Google Play will showcase selected high-quality + Auto apps for easy discovery by users in Google Play. Here’s how you + can participate and deliver an Android Auto app that users will enjoy: +
+ ++ Before you can upload your APK and publish the app for review, the developer account owner + must agree to the + Android + Auto terms from the Pricing and Distribution section of the + Developer Console. Agreeing to the terms means that you want your app to be made available + to Android Auto users through Google Play, and that + your app meets Auto + App Quality guidelines. +
+ ++ Your Auto app can be uploaded only after you have agreed to the terms. The following describes + which apps are determined to be Auto apps: +
+ +com.google.android.gms.car.application
+ metadata entry in the manifest with auto capabilities that the app uses. For more information
+ about configuring your app for use with Android Auto, see
+ Getting Started with Auto.
+ + When you've built your release-ready APK and tested to ensure that it meets + all of the Auto App + Quality guidelines, upload it to the Developer Console. Update your store + listing with any additional Auto functionality information, and set distribution options as + needed. If you aren't familiar with how to prepare for launch on Google Play, + see the Launch + Checklist. +
+ ++ After you agree to the terms and save the changes, you can upload and publish your app as usual. + Before making the app available to Android Auto users, Google Play submits + your app for review against the Auto App Quality criteria + and notifies you of the result. If your app is approved, Google Play makes that app + available to Android Auto users. See the next section for details on how to track the approval + status of your app. +
+ ++ Note that the review affects the availability of your app to other devices in + Google Play Store — on phones and tablets, for example. + If you have an existing app that includes updates to the phone/tablet component, + the Android Auto component must pass review before the updated app + is made available on the Google Play Store. +
+ ++ Here are the steps to agree to Android Auto terms in the Developer Console: +
+ +
+ + Agree to terms for Auto: Include your app in Android Auto by agreeing to the + terms from the Developer Console. +
++ Your app will be reviewed for compliance with driver distraction guidelines and the + technical and quality criteria described above. This detailed review process may take + more time than you are accustomed to when submitting phone/tablet apps. + Until your app is approved, your app or app update won’t be published to the Google Play Store. + After a successful review, your app will be published and made available on the Google Play + Store. +
+ +If your app is not accepted, you’ll receive a notification email sent to your + developer account address, with a summary of the areas that you need to address. When + you’ve made the necessary adjustments, you can upload a new version of your app to the Developer + Console. +
+ ++ Note that if the submitted app is an update to an existing app and your updated app does not meet + the review criteria, the update is rejected and the existing app remains published in the Google + Play Store. +
+ +To understand how your apps are evaluated, please see the Auto App Quality document.
+ + +