Stay organized with collections
Save and categorize content based on your preferences.
In AAOS, the permissions flow is the same as
granting permissions on Android Auto,
except the user sees permission details on the car screen instead of the
phone.
Sample flow
User action
Where action is performed
Step count after action
The user opens your app, and they must grant permissions.
Landing template (not shown)
1
The user selects the option to grant app permissions.
Message template
2
The user sees a system permissions dialog on the car screen and grants
permissions.
Message template with toast (refresh)
2
The app returns to the landing template.
Landing template (in this case, the Place List template)
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eIn Android Automotive OS, the app permissions process mirrors that of Android Auto, with the distinction of user interaction occurring on the car's display instead of the phone.\u003c/p\u003e\n"],["\u003cp\u003eWhen an app requires permissions in AAOS, users are guided through a streamlined flow involving a landing template, a message template prompting for permission, and a system permissions dialog on the car screen.\u003c/p\u003e\n"],["\u003cp\u003eUpon granting permissions, the app seamlessly transitions back to its initial landing template or, in this specific scenario, the Place List template, potentially initiating a new task.\u003c/p\u003e\n"]]],[],null,[]]
