AI-generated Key Takeaways
-
Drivers can use a PIN code or one of three other methods to sign in using the provided Sign-in template within their car's interface.
-
The flow includes a Long Message template which can display detailed information like the Privacy Policy or Terms of Service without impacting the step count.
-
Android Auto utilizes parked-only templates for sign-in and long messages, meaning these actions do not increase the task's step count.
-
Users initiate the sign-in process on their car's screen, are prompted with a QR code to scan on their phone, then continue the sign-in process on their phone.
-
After completing sign-in or reviewing information, the user is returned to the main landing screen of the application within their vehicle's interface.
Use the Sign-in template to prompt the user to sign in with a PIN code (as shown below) or one of the other 3 sign-in methods.
Add the Long Message template to provide details such as text of the Privacy Policy or Terms of Service. These templates are both parked-only templates, so they don't increment the step count.
Sample flow
| User action | Where action is performed | Step count after action |
|---|---|---|
| The user taps a button to sign in to the app. | Landing template (not shown) | 1 |
| To sign in, the user sees a QR code that they must capture on their phone. | Sign-in template (parked-only template)
|
1 |
| The user scans the QR code, which takes them to the sign-in process on their phone screen. | No template (task continues on phone) | 1 (task paused) |
| The user reads the app's privacy policy (if required). | Long Message template (parked-only)
|
1 |
| The app returns to the landing template. | Landing template (in this case, List template included in the Map + Content template)
|
1 (new task) |
