Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Pahami berbagai cara aplikasi Anda dapat berkomunikasi dengan pengguna, lalu pilih
opsi yang paling sesuai untuk setiap kasus penggunaan.
Aplikasi Anda dapat berkomunikasi dengan pengguna menggunakan toast,
notifikasi, dan peringatan navigasi, serta menggunakan template
berorientasi pesan atau input suara. Ikuti praktik terbaik saat menggunakan input suara
di aplikasi Anda untuk melindungi privasi pengguna dan menandai pengalaman.
Saat aplikasi Anda perlu berkomunikasi dengan pengguna, pilih metode yang paling sesuai dari
metode yang tersedia:
Fitur input suara memungkinkan aplikasi mengakses mikrofon mobil guna mengumpulkan input
audio untuk tujuan seperti membuat asisten dalam aplikasinya sendiri.
Cara kerjanya
Ikon input suara akan muncul untuk memberi tahu pengguna bahwa mereka dapat
memberikan input suara.
Pengguna meminta input suara (dalam hal ini melalui ikon mikrofon di strip tindakan).
Overlay akan muncul, menandakan bahwa perekaman sedang berlangsung.
Pengguna dapat menghentikan perekaman dengan menutup overlay, atau mereka dapat berhenti
berbicara, dan pada saat itu aplikasi harus berhenti merekam.
Ingatlah praktik terbaik berikut saat Anda mengembangkan aplikasi:
Dapatkan izin terlebih dahulu. Pastikan pengguna telah memberikan izin kepada aplikasi
Anda untuk mengakses mikrofon mobil (idealnya sebelum perjalanan dimulai).
Berikan titik entri. Beri pengguna cara untuk memulai input suara, seperti
ikon mikrofon di strip tindakan. Kemudian, tunggu hingga mereka memulai
proses.
Beri merek pada pengalaman. Saat membuat asisten dalam aplikasi, jelaskan bahwa
asisten tersebut adalah asisten khusus untuk aplikasi Anda.
Hentikan saat pengguna melakukannya. Setelah pengguna selesai berbicara, berhenti merekam.
[null,null,["Terakhir diperbarui pada 2025-07-25 UTC."],[[["\u003cp\u003eApps can communicate with users through various methods, including toasts, notifications, navigation alerts, message templates, and voice input, each suited for specific use cases.\u003c/p\u003e\n"],["\u003cp\u003eWhen utilizing voice input, prioritize user privacy by obtaining microphone permissions, providing a clear entry point for voice interaction, and branding the experience as app-specific.\u003c/p\u003e\n"],["\u003cp\u003eVoice input enables users to interact with apps using the car's microphone; the process involves an overlay indicating recording, which the user can dismiss or allow the app to stop automatically.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers should refer to detailed documentation on notifications and their types for navigation apps, Android for Cars, and Android Automotive OS for a comprehensive understanding.\u003c/p\u003e\n"],["\u003cp\u003eVehicle OEMs have the authority to determine whether navigation Heads-up notifications are displayed within the Android Automotive OS version of the app.\u003c/p\u003e\n"]]],[],null,["# Plan communications\n\n\u003cbr /\u003e\n\nUnderstand the range of ways your app can communicate with users, then choose\nthe most appropriate option for each use case.\n\nYour app can communicate with users by means of using toasts,\nnotifications, and navigation alerts, as well as by using message-oriented\ntemplates or [voice input](#voice). Follow best practices when using voice input\nin your app, to protect user privacy and brand the experience.\n\nWhen your app needs to communicate with users, choose the most appropriate of\nthe available methods:\n\n| Communication method | Format | Example use case |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|\n| [Message template](/cars/design/create-apps/apps-for-drivers/templates/message-template) | Brief message with icon or image + up to 4 actions | Error message |\n| [Long Message template](/cars/design/create-apps/apps-for-drivers/templates/long-message-template) | Long, scrollable message to be read while parked | Legal text for permissions |\n| [Toast](https://developer.android.com/guide/topics/ui/notifiers/toasts) | Pop-up showing very brief text | Telling the user to continue a flow on the phone when parked |\n| [Voice input](#voice) | Input provided via microphone and recorded by the app | User makes a request of the app while driving |\n| [Navigation alerts](/cars/design/create-apps/apps-for-drivers/templates/navigation-template#alerts) | Brief message with optional actions on the [Navigation template](/cars/design/create-apps/apps-for-drivers/templates/navigation-template) (doesn't block navigation info) | Suggesting a change in route |\n| [Heads-up notifications (HUNs)](/cars/design/android-auto/product-experience/system-ui/notifications#heads-up_notification_hun) | Temporary notification card with brief text + up to 2 actions, able to deep-link to relevant parts of the app | Highly important update worth disrupting other tasks (use outside of the Navigation template) |\n\nMore about notifications:\n\n- Be aware that vehicle OEMs can decide whether to display navigation HUNs in the AAOS version of your app.\n- For details about types of notifications used by navigation apps, refer to [Navigation notifications: Turn-by-turn (TBT) and regular](/cars/design/create-apps/apps-for-drivers/templates/navigation-template#notifications).\n- For technical details about displaying notifications in Android for Cars, refer to [Display notifications](https://developer.android.com/training/cars/apps#display-notifications).\n- And for additional details relevant to AAOS, visit [Notifications on Android Automotive OS](https://developer.android.com/training/cars/notifications).\n\nVoice input details\n-------------------\n\nThe voice input feature lets apps access the car's microphone to gather audio\ninput for purposes such as creating their own in-app assistant.\n\n### How it works\n\nA voice input icon appears to inform the user that they can provide voice input.\n\n1. The user requests voice input (via the microphone icon in the action strip, in this case).\n2. An overlay appears, signaling that recording is in process.\n3. Users can stop the recording by dismissing the overlay, or they can stop talking, at which point the app should stop recording.\n\nFor a sample flow showing this process, see\n[Communicate with the app by voice](/cars/design/create-apps/sample-flows/communicate-with-voice).\n\n### Best practices\n\nKeep the following best practices in mind as you develop apps:\n\n- **Get permission first.** Make sure the user has granted permission for your app to access the car's microphone (ideally before the drive starts).\n- **Provide an entry point.** Give the user a way to start voice input, such as a microphone icon in the action strip. Then, wait for them to initiate the process.\n- **Brand the experience.** When creating an in-app assistant, make clear that it's an assistant specific to your app.\n- **Stop when the user does.** When the user is done talking, stop recording."]]
