[null,null,["Last updated 2024-07-23 UTC."],[[["\u003cp\u003eThe Sign-in template provides options for users to sign in to car apps while parked, supporting methods like provider sign-in, username/password, PIN code, and QR code.\u003c/p\u003e\n"],["\u003cp\u003eThis template includes elements like header, primary text, sign-in method selection, additional text (disclaimers, terms of service), and buttons.\u003c/p\u003e\n"],["\u003cp\u003eWhen the car is in motion, the sign-in template is hidden to avoid driver distraction, and developers might consider options like guest mode access.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers must include at least one sign-in method and are recommended to prioritize user-friendliness by using input fields solely for sign-in and opting for the shortest, most popular sign-in flows.\u003c/p\u003e\n"]]],[],null,["# MUST, SHOULD, and MAY for apps\n\n\u003cbr /\u003e\n\nUX requirements are expressed as instructions that you MUST, SHOULD, or MAY\nfollow. At a high level, you can understand these labels as follows:\n\n|------------|---------------------------------------------------------------------------------------------------------------------------------------------------|\n| **MUST** | Required (enforced either in the API or in [Android app quality for cars](https://developer.android.com/docs/quality-guidelines/car-app-quality)) |\n| **SHOULD** | Recommended |\n| **MAY** | Optional |\n\nFor details, including a discussion of MUST NOT and SHOULD NOT, visit\n[Meaning of Must, Should \\& May](/cars/design/intro-terms#meaning_of_must_should_may).\n| **Note:** Be aware that Android app quality for cars specifies additional requirements beyond the design-related requirements discussed here. App developers are responsible for complying with all requirements: App quality for cars and those discussed here."]]