[null,null,["上次更新時間：2025-08-26 (世界標準時間)。"],[],[],null,["Keep in mind the following best practices when designing sign-in experiences.\n\nUse Credential Manager\n\nEach of [Credential Manager's](/identity/sign-in/credential-manager) built-in authentication methods are fully\nstandalone, requiring only the users watch and a data connection for\nauthentication. No other authentication method can offer this benefit.\n\nUse Credential Manager as the base of your authentication solution.\n\nPrimary options: Credential Manager built-ins\n\nImplement passkeys as the foremost option in Credential Manager to provide\nstate-of-the-art security and simplicity to your users.\n\nImplement the complete experience by adding passwords and Sign in With Google as\nwell. \n**Fig. 1a:**Passkeys **Fig. 1b:**Passkeys, passwords, \\& Sign in with Google\n\nSecondary options\n\nOffer at least one secondary option to handle users dismissing Credential\nManager. Provide at least two distinct sign-in options in total.\n\nApps without multiple sign-in methods create a difficult user experience. For\nexample, an app that offers only a \"Sign in on phone\" option fails if the user's\nphone is not nearby. \n**Fig. 2a:**Tap 'Dismiss' for backups **Fig. 2b:**Backup authentication\n\n**Special Case:** [Automatic data layer authentication](/training/wearables/apps/auth-wear#tokens) is the only secondary\noption which is acceptable to precede Credential Manager in your UX. This comes\nwith several important caveats:\n\n1. You must offer at least one other authentication method beyond this because it works only on paired watches with a corresponding mobile app installed.\n2. You must fully automate the token exchange for the user, and you must not present any UI to the user beforehand. In other words, you should make the authentication process fully automatic from the user's perspective.\n3. If this method fails, either the user is not logged in on a paired phone, or there is no paired phone to begin with. Don't alert the user there was a failed attempt, instead navigate directly to Credential Manager.\n\nPrompt users correctly\n\n**For apps requiring sign-in for all functionality:**\nImmediately present Credential Manager as the first screen to a signed-out user,\nwithout any preceding UI.\n\n**For apps offering functionality without sign-in:**\nDelay presenting Credential Manager until necessary. Provide as many features as\npossible without requiring sign-in. When authentication becomes essential,\ndisplay a 'sign in' button to launch Credential Manager. If sign-in fails, offer\nthe option to skip authentication.\n\nAuthentication best practices\n\nExplain sign-in benefits\n\nFor apps that delay user sign-in until it becomes essential, clearly explain the\nbenefits of signing in. Use the surrounding UI context to articulate the value\nto the user; don't assume they understand why signing in is beneficial.\n\nNever refer to Credential Manager by name in your UI. \ncheck_circle\n\nDo \nProvide context by asking for sign-in after the user initiates an action. \ncancel\n\nDon't \nDisplay sign-in without explaining why sign-in is beneficial.\n\nStreamline\n\nStreamline the authentication process by:\n\n1. Using Credential Manager\n2. Reducing the number of steps needed in secondary sign in options\n3. Keeping users signed in for as long as possible (within your privacy and security requirements)\n\ncheck_circle\n\nDo \nUse Credential manager \ncheck_circle\n\nDo \nDisplay all secondary options together. \ncheck_circle\n\nDo \nStay signed in\n\nSign-in status and confirmations\n\nWhen using secondary, non-Credential Manager options, display a message that\nalerts the user that they are being signed in the first time the app is opened,\nthen display a confirmation message upon successful sign-in. \ncheck_circle\n\nDo \nTell user they're being signed in. \ncheck_circle\n\nDo \nShow a confirmation."]]
