AI-generated Key Takeaways
-
In 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.
-
When 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.
-
Upon 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.
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)
|
1 (new task) |
