ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
Additional requirements for Google Meet Add-ons integrations
2
This document is an extension of the information found at Additional requirements for specific app integrations.
3
First complete all the steps under Requirements for all apps before completing the Meet-specific requirements.
4
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
5
App integrationCategoryCriteria
6
Google Meet Add-onFunctionality
7
The add-on login and user journeys MUST be functional even if third-party cookies are disabled.
8
The add-on MUST adhere to the general Google Workspace Marketplace approval guidelines found on their site.
9
(Recommended) Add-ons SHOULD conform to the WCAG 2.1 level AA guidelines on accessibility. Add-on developers will self-report that this requirement is met at the time of submission and that the add-on continues to stay in conformance with future changes to the add-on.
10
The add-on MUST provide functionality relevant to the operation of, or participation in, a meeting.
11
The add-on MUST NOT do anything that makes users leave the meeting, such as refreshing the browser.
12
If using multi-player experience, the add-on MUST allow for all participants to collaborate on content even if permissions are not set in advance. Permission adjustment MUST be available during the collaborative add-on session.
13
(Recommended) The add-on SHOULD allow the user to set permissions before the content is shared.
14
(Recommended) The add-on SHOULD allow users to enter the add-on experience by screen sharing the app.
15
The add-on MUST handle the cancellation of the start collaboration flow and allow the user to re-initiate the start of the collaboration from the app.
16
The add-on MUST provide a side panel for sign-in and and set up of the collaboration experience.
17
Google Meet Add-onUser experience
18
If the add-on requires a license or subscription: A user-friendly message MUST be shown to the user when the user doesn't have a license.
19
The message MUST clearly state the reason the add-on cannot be used and suggest a course of action for the user to remedy the situation.
20
The Google Workspace Marketplace listing for the add-on MUST specify details about the license and subscription requirements that may be required to use the add-on. If the add-on has a paid tier, the Google Workspace Marketplace listing MUST provide a link to a webpage that offers more information about pricing or how to contact a salesperson.
21
The add-on MUST sign in the user on subsequent visits without showing a login prompt (within a 5-minute time window of the original sign in).
22
When the user isn't already signed in, the add-on MUST present the One Tap sign-in prompt found at https://developers.google.com/identity/gsi/web/guides/display-google-one-tap and a "Sign In with Google" fallback found at https://developers.google.com/identity/authentication. In addition to the "Sign in with Google" mechanism, other login options may be offered.
23
(Recommended) The add-on SHOULD display who the currently signed-in user is.
24
(Recommended) Localization choice: language SHOULD be based on local preference set by the browser when available.
25
The add-on MUST have responsive design that can adapt content to different sizes.
26
The add-on user journeys MUST to be functional even if third-party cookies are disabled.
27
The add-on MUST NOT have horizontal scrolling within the iframe.
28
The add-on MUST design a content creation and selection flow that's fully embedded into the side panel. Content selection MAY be through a pasted link.
29
(Recommended) Content selection SHOULD be through a content browsing interface featuring recently accessed content.
30
(Recommended) If the side panel is no longer needed, the add-on SHOULD close the side panel after launching to the main stage.
31
If an add-on wants to utilize the main stage, the add-on MUST be designed for multiplayer experiences and allow for content to be manipulated by multiple participants at the same time. For single-player experiences, the developer should use the side panel.
32
Google Meet Add-onGraphics
33
The brand logo of the add-on needs to be in a size and styling such that it's identifiable in the Meet side panel.
34
Suitable dark mode logo URLs MUST be specified in the add-on manifest
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100