About this Video

• Video Title: How To Make a Demo Video for Google OAuth
• Channel: CloudSponge
• Speakers: Heather
• Duration: 00:05:58

Introduction

This video provides a step-by-step guide on creating a demo video and justifying scopes for Google OAuth verification. It addresses potential pushback from Google regarding requested scopes and offers a workaround.

Key Takeaways

• Workaround for Google Scope Pushback: A quick method is shown to prevent Google from rejecting scope requests before video submission. This involves using spongecrunch.com and submitting without clicking on the scopes being verified.
• Demo Video Creation: The video details how to create a demo video showcasing user interaction with Google contacts, emphasizing the importance of clearly displaying the client ID and privacy policy.
• YouTube Upload and Unlisting: The created demo video should be uploaded to YouTube as an unlisted video.
• Scope Justification: The process of justifying requested scopes to Google is explained, emphasizing the need to clearly articulate the application's use of the requested Google Contact scopes (both saved contacts and "other contacts"). Canned response examples are provided.
• Verification Submission and Follow-up: After completing the video, justifying scopes, and double-checking all information, the application is submitted for Google verification. The speaker advises on how to handle potential pushback from Google.

The transcript doesn't explicitly state why this workaround is necessary to avoid Google rejecting scope requests. It only explains the how. The implication is that Google's initial review process might flag certain scope requests, and this workaround allows the application to proceed to the next steps (video submission and detailed justification) before Google encounters those potentially problematic scopes.

The video explains a process to avoid Google rejecting your OAuth application's scope requests before you even submit your demo video. This process involves using a website (spongecrunch.com, which is likely a placeholder for the user's own website) during the Google OAuth application setup. Instead of selecting the scopes (permissions your app requests from Google) at that stage, the video instructs the user to bypass that selection. Essentially, the user submits the initial application without explicitly declaring the specific scopes they need, sidestepping a potential early rejection by Google. The justification for these scopes, and the demonstration of their use, is then provided later through the demo video.

The justification for the scopes is explained later in the video. The speaker states you need to tell Google why you need the scopes and what you're going to do with them. Specifically, the example given is to explain that the app needs access to Google Contacts so users can select friends to send referrals. The justification should explain the app's use case, whether it's for referrals, newsletter sign-ups, or other purposes. The speaker also notes that Google splits their scopes into two categories: "saved contacts" and "other contacts," and advises explaining the need for "other contacts" access because users likely interact with many people not explicitly saved in their address books.