Stay organized with collections
Save and categorize content based on your preferences.
This page describes the best practices developers should observe when using
sign-in methods for Google Meet add-ons. It lets users create an account or
sign in to a website by eliminating the long registration or authentication
process.
Here are some important tips developers can use when implementing sign-in
methods for Meet add-ons:
If your app must authenticate the user through other mechanisms, or
re-authenticate the user during Google sign-in or One Tap to link with an
existing account, do that in a dialog window. Don't display user-password
sign-in forms directly in iframes.
Always use the default rendering of the One Tap prompt for
Meet add-ons.
[[["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-12-19 UTC."],[[["Google One Tap sign-in is the strongly recommended method for Google Meet add-ons to streamline user authentication."],["Developers should include a fallback Google sign-in button in case One Tap isn't available or suitable for all users."],["Authentication or re-authentication beyond Google sign-in/One Tap should occur in a separate dialog window, avoiding direct user-password forms within iframes."],["For Meet add-ons, developers must use the default rendering of the One Tap prompt for consistent user experience."]]],[]]
