gaelic-ghost Google Meet Collaboration Workflow
Workflow
- Choose the smallest correct surface: web add-on for in-meeting shared collaboration, REST API for meeting spaces and post-conference artifacts, Workspace Events for subscriptions, or the Media API only for an explicitly accepted Developer Preview evaluation.
- Define Workspace identity, OAuth scopes, organizer and participant data access, add-on deployment, and data retention before implementation.
- For an add-on, design shared state and participant controls as collaboration features rather than as an unattended meeting bot.
- For REST/event work, separate meeting-space management from artifact processing and avoid using conference data for user performance evaluation.
- For Media API evaluation, record preview status, consent, media handling, cost, and rollback conditions. Do not present preview behavior as production stable.
- Validate in a test Workspace and meeting: installation, participant join, shared state, event subscription, artifact availability, authorization failure, and removal.
Source And Handoffs
Start with the Google Meet SDK and API overview. Hand web implementation to the web workflow and backend work to the chosen server skill.