All Mocha apps come with Google sign-in already working. Your users can log in with their Google accounts immediately—no setup required.Why this works well:
Zero configuration needed
No technical setup or Google approvals
Your app is ready to accept user logins right away
The trade-off:
When users sign in, they’ll see “Mocha” in the Google sign-in screen instead of your app’s name and logo.
If you are a Silver or Gold subscriber and want your users to see your app’s branding when signing in, you can connect your own Google OAuth client. This requires creating credentials through Google, but gives you complete control over the sign-in experience.What you’ll gain:
Your app name and logo in the Google sign-in flow (instead of Mocha’s)
Professional, branded authentication experience
What you’ll need to do:
Create a Google Cloud account (free)
Set up a Google OAuth client (we’ll walk you through this)
In Mocha, in your application settings, enter your client ID and client secret in the “Google Sign In” section
We use the language “Google OAuth clients” but sometimes these are called “OAuth applications” or “credentials” by Google. These are simply the connection settings that let your app use Google sign-in with your own branding.
Search for and navigate to the “OAuth consent screen”
Click on “Create OAuth client”
Choose “Web application” as the application type
Add Mocha’s redirect URI https://getmocha.com/u/oauth/google/callback as one of the “Authorized redirect URIs” — this is critical for sign in to work
In your Mocha project, go to the “Google Sign In” section in the settings dialog and paste the client ID and client secret into the appropriate fields. Click “Add OAuth client”
If your configuration is correct and your application is approved by Google, your app will immediately start using your custom OAuth client for signing in
The “Branding” section in the Google Developer Console allows you to customize how your app appears in the Google sign-in flow. You can add your app’s name, logo, and other branding elements.Note: DO NOT share the client ID or client secret with anyone! They are sensitive passwords. The values in the images above were never used and have been deleted.