Adding Google sign-in to your native mobile app lets users log in or sign up with their existing Google account — no extra password required. This guide walks you through everything you need: installing the plugin, configuring your Google credentials, and wiring up the login workflow in your native app.
What you'll need
A Bubble app with a native mobile app set up
A Google Cloud account to generate your API credentials
The Bubble-made Google plugin installed in your app
How Google auth works in Bubble native mobile
Google auth in a native mobile app works differently from the web. Bubble's Native Mobile Beta uses a browser-based OAuth redirect flow — not a true native Google SDK integration. Here's what happens when a user taps "Sign in with Google":
The user taps "Sign in with Google" in your native app.
Bubble opens a web browser (in-app or system) pointed at your Bubble web app's OAuth endpoint.
Google handles authentication there.
Google redirects back to your app via the Bubble redirect URI (/api/1.1/oauth_redirect).
The user is logged in and returned to the native app, still authenticated.
⚠️ Don't use the standard "Sign up/in with OAuth provider" action in your native app — this causes Error 400 and redirect mismatches on mobile.
The dynamic ?on_login=... parameter Bubble appends can't be pre-registered in Google Cloud Console. Use the Signup/login with a web browser action instead (covered in Step 4).
Step 1: Install the Google plugin
In the Bubble editor, open the Plugins tab and click Install new plugins.
Search for Google. You can check the Login service checkbox to filter results.
To confirm it's the official plugin, scroll to Built by in the filters and select Official — look for the Bubble logo in the bottom-right corner of the plugin card.
Click Install.
Step 2: Set up your Google API credentials
You'll need two credentials from Google Cloud: an App ID (Client ID) and a Secret Key. These authenticate your app's connection to Google.
App ID (Client ID): the public identifier for your app. You don't need to keep this secret.
Secret Key: works like a password between your app and Google's servers. Keep this strictly private — if it's ever exposed, revoke it immediately and generate a new one.
To generate these credentials, follow the official Google documentation:
External page: Using OAuth 2.0 to Access Google APIs
Exposed secret key? Revoke it right away and create a new one. Once you've updated the key in your plugin settings, make sure to deploy your changes to Live.
Step 3: Configure the Google plugin in Bubble
In the Bubble editor, go to Plugins and click on the Google plugin.
Paste your App ID into the App ID field.
Paste your Secret Key into the Secret key field.
If you want to test without affecting live data, add your development tokens in the designated fields — Bubble will use these automatically in preview mode.
Step 4: Set up the login workflow in your native app
Native mobile apps have a dedicated action for handling OAuth login: Signup/login with a web browser. This uses a page from your web app to handle the login flow, so you don't need to build a separate version for mobile. It supports Google OAuth, email/password login, and 2FA out of the box.
In your native app's login view, create a button (e.g. "Continue with Google").
Open the workflow editor and add the Signup/login with a web browser action.
Set the page to the login page on your web app where Google sign-in is configured.
When a user taps the button, a web browser will open for them to authenticate with Google. Once they're done, the browser closes automatically and they're logged in.
The Signup/login with a web browser action works the same way for new sign-ups and returning logins — no need to build separate flows for each.
FAQ
What if I accidentally expose my App ID?
No action needed. The App ID is a public identifier and doesn't need to be replaced if it's exposed.
What if I accidentally expose my Secret Key?
Revoke it immediately in Google Cloud and generate a new one. Update the key in your plugin settings and deploy your changes to Live.
Does Google authentication work the same on iOS and Android?
Yes. The Signup/login with a web browser action and the Google plugin work across both platforms.
