How to make an app · Integration guide

How to add Login with Google
to your app, the right way

To add Login with Google, create an OAuth client in Google Cloud and configure the consent screen, then use Credential Manager on Android, the Google Sign-In SDK on iOS, or Google Identity Services on the web. Send the returned ID token to your server and verify it before creating a session. On iOS, Apple's guidelines require an equivalent privacy-focused login option, such as Sign in with Apple, if you offer Google.

By , FounderUpdated 5 min read

Share

Quick answer: How do I add Google login to my app?

  1. Google Cloud — create a project, consent screen and OAuth client IDs per platform.
  2. Android — Credential Manager is the current recommended API.
  3. iOS — Google Sign-In SDK; add Sign in with Apple to meet App Store rules.
  4. Web — Google Identity Services (the button and One Tap).
  5. Server — verify the ID token, then create your own session.

Key takeaways

  • One-tap sign-in removes passwords, a common reason users abandon sign-up.
  • An ID token is only trustworthy after your server verifies its signature, audience and expiry.
  • Link accounts by verified email carefully to avoid duplicate or hijacked accounts.
  • Firebase Authentication or a similar service handles most of this for small teams.
  • Ask for the minimum scopes — basic profile and email are enough for login.

Every extra field on a sign-up form is a small exit door. Passwords are the biggest one: people forget them, reuse them and abandon forms to avoid creating them. "Continue with Google" replaces all of that with one tap. Done properly, it is also more secure than a homemade password system. Done carelessly, it is a way to log in as someone else.

How do I add Google login to my app? At a glance: Google Cloud; Android; iOS; Web; Server.
At a glance: How do I add Google login to my app?

How it works in one picture

Diagram of 6 steps for how it works in one picture: 1. The user taps Continue with Google in your app.; 2. Google shows its account picker and consent; the user chooses an account.; 3. Your app receives an ID token; 4. Your app sends the ID token to your server.; 5. Your server verifies the token an
How it works in one picture
  1. The user taps Continue with Google in your app.
  2. Google shows its account picker and consent; the user chooses an account.
  3. Your app receives an ID token — a signed statement from Google about who the user is.
  4. Your app sends the ID token to your server.
  5. Your server verifies the token and finds or creates the user.
  6. Your server issues its own session to the app.

The critical step is 5. An ID token is only trustworthy after your server has checked it4.

Step 1: set up Google Cloud

Checklist: Step 1: set up Google Cloud — Create a project in the Google Cloud console; Configure the OAuth consent screen: app name, logo, support email, privacy policy and authorised domain; Request only the openid, email and profile scopes for login; Create OAuth client IDs for each platform: Andr
Step 1: set up Google Cloud
  • Create a project in the Google Cloud console
  • Configure the OAuth consent screen: app name, logo, support email, privacy policy and authorised domain
  • Request only the openid, email and profile scopes for login
  • Create OAuth client IDs for each platform: Android (with your package name and SHA-1 signing fingerprint), iOS (bundle ID), and Web (also used by your server to verify tokens)

Step 2: add it to each platform

How to add Sign in with Google on each platform
PlatformRecommended approachNotes
AndroidCredential Manager with the Google ID option1Replaces the older Google Sign-In for Android library
iOSGoogle Sign-In SDK for iOS3Pair with Sign in with Apple for App Store rules
WebGoogle Identity Services — the Sign in with Google button and One Tap2Replaces the older Google Sign-In JavaScript library
Flutter / React NativeOfficial or well-maintained plugins wrapping the aboveOr Firebase Authentication

Step 3: verify the token on your server

Using Google's server library, check that the token's signature is valid, the audience matches your client ID, the issuer is Google, and it has not expired4. Then use the token's stable user ID (sub) as the link to your user record — not the email, which can change.

Step 4: handle account linking

Step 4: handle account linking: Same email, existing…; Google first, password later; Unverified email.
Step 4: handle account linking

Same email, existing password account

Ask the user to sign in with their password once to link Google, rather than silently merging.

Google first, password later

Let them add a password from settings if they want one.

Unverified email

Only trust an email for linking if the token marks it as verified.

Step 5: meet Apple's rule

If your iOS app uses a third-party login such as Google for the main account, Apple's guideline 4.8 generally requires you to also offer an equivalent option with privacy protections — Sign in with Apple meets it5. Plan for both buttons from the start.

Design the sign-in screen well

Checklist: Design the sign-in screen well — Use Google's official button styles and wording ("Sign in with Google" / "Continue with Google"); Show social options above email, with equal visual weight for Google and Apple on iOS; Explain why an account is needed; Handle cancel and error states gracef
Design the sign-in screen well
  • Use Google's official button styles and wording ("Sign in with Google" / "Continue with Google")
  • Show social options above email, with equal visual weight for Google and Apple on iOS
  • Explain why an account is needed — or let people explore before signing in
  • Handle cancel and error states gracefully

Sign-up is often where onboarding leaks most. An onboarding audit finds where people drop off.

Key terms, defined

OAuth 2.0 — the standard for delegated authorisation. OpenID Connect — the identity layer on top of OAuth used for sign-in. ID token — a signed token describing the signed-in user. Client ID — your app's identifier with Google. Scope — the data or access requested. Credential Manager — Android's unified sign-in API.

Frequently asked questions

Is Login with Google free?

Yes. Google does not charge for Sign in with Google. If you use a managed auth service such as Firebase Authentication, check its pricing for your expected number of monthly active users.

What is Credential Manager on Android?

Credential Manager is Android's Jetpack API that brings passwords, passkeys and federated sign-in such as Sign in with Google into one interface. Google recommends it for new Sign in with Google integrations on Android.

Do I need Sign in with Apple if I add Google login?

On the App Store, apps that use a third-party or social login for the primary account generally must also offer an equivalent login option with privacy protections, and Sign in with Apple meets that requirement. There are exceptions, such as apps using only your company's own account system.

How do I verify a Google ID token?

On your server, use Google's client library to verify the token's signature, check that the audience matches your client ID, the issuer is Google, and it has not expired. Then use the stable user ID ('sub') to find or create the user.

Should I use Firebase for Google login?

For many small and medium apps, yes. Firebase Authentication wraps Google, Apple, phone and email sign-in, handles tokens and sessions, and works across Android, iOS, web and Flutter. Larger teams may prefer their own auth service or another identity provider.

Why does Google show an 'unverified app' warning?

Apps requesting sensitive or restricted scopes need Google's verification. For basic login, request only the openid, email and profile scopes, complete your consent screen with a privacy policy and domain, and publish it.

Sources

  1. Android Developers — Authenticate users with Sign in with Google (Credential Manager)
  2. Google for Developers — Sign in with Google for Web (Google Identity Services)
  3. Google for Developers — Google Sign-In for iOS
  4. Google for Developers — Verify the Google ID token on your server side
  5. Apple Developer — App Store Review Guidelines (4.8 Login Services)
  6. Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Before you launch

Make sure the first screen makes sense.

A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.

Free certification

Turn what you know into a credential.

Free, test-based UX, UI and product certifications. Answer real product scenarios, graded on our server, and earn a founder-signed certificate anyone can verify and you can add to LinkedIn.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy