Signing in on mobile
Google, Apple, and email-OTP sign-in on the installed mobile app — how each works, what's different from the web flow, and what to do when things go wrong.
The installed Android / iOS app uses a native sign-in screen with three options: Continue with Google, Continue with Apple (iOS only), and Continue with email. Each routes through a slightly different mechanism to handle the security constraints of running inside a mobile WebView. The Apple button stays hidden on Android in v1.
Google sign-in
When you tap Continue with Google, the app opens Google’s sign-in screen in a system browser tab (Chrome Custom Tabs on Android, the Safari sign-in sheet on iOS). This is intentional — earlier app versions ran the OAuth round-trip inside the WebView, which broke because mobile WebViews treat cross-site redirects differently from a regular browser. The system browser handles the round-trip correctly, then hands you back into the app via a deep link.
What you’ll see: tap the button → a Chrome tab (or Safari sheet) opens → pick a Google account → momentary loader → the tab closes automatically and the app continues with a “Finishing sign-in…” splash for about a second → you land on your home dashboard. If the tab closes without signing you in, you cancelled the flow — tap Google again to retry.
If Google sign-in fails: you’ll see an error message and stay on the sign-in screen. The most common cause is a slow network during the round-trip. Try again, or fall back to email below.
Apple sign-in (iOS only)
On an iPhone or iPad, Continue with Apple triggers iOS’s native Sign in with Apple sheet — you’ll be asked to authenticate with Face ID, Touch ID, or your Apple ID password. No browser tab opens; this is the system-native flow Apple requires for App Store apps. After you authenticate, the app finishes the sign-in in the background and lands on your home dashboard.
The Apple button doesn’t appear on Android — Apple Sign In on Android isn’t supported in v1. Android users get Google + email.
Email sign-in (6-digit code)
Tap Continue with email, enter your address, and tap Send code. Within ~10 seconds you’ll get an email with a 6-digit code. Open it on the same device — iOS shows the code as a one-tap chip above the keyboard, and Android Messages auto-fill works the same way. Tap it and the app verifies automatically the moment the 6th digit lands. No need to tap a separate “Sign in” button.
If the code doesn’t arrive: check your spam folder, then tap Resend code on the verification screen. There’s a 30-second cooldown between resends to prevent accidental duplicate sends.
What hasn’t changed
Once you’re signed in, your session works exactly the same as the web — same workspaces, same projects, same permissions, same notifications. The sign-in mechanism is the only thing the app does differently from itzseo.com in a regular browser tab. Sign out lives under More → Session → Sign out in the bottom nav.