iOS accounts & sign-in
Letting people into the app — Apple and Google sign-in, email flows, and sessions that behave.
What we build
Sign in with Apple (which Apple requires if you offer any other social login), Google Sign-In, and email with verification and reset. Includes the session lifecycle — staying signed in, expiring safely, and surviving a token refresh. Decline this only if the app has no accounts at all. The identity provider and token side lives in authentication & identity integration; this service is the in-app experience.
What you get
- Sign in with Apple working on a real device
- Google Sign-In working on a real device
- Sessions that survive an app restart and refresh expired tokens without signing the user out, each covered by a test
How the work unfolds
- Integrate Sign in with Apple and Google Sign-In
- Build email auth flows with verification
- Wire the session lifecycle to the backend
What shapes the price
Before you see a number, our scoping conversation asks:
- Should people be able to sign up with an email address and password, as well as Apple and Google? Email auth brings verification and password-reset flows — up to three days. If authentication & identity integration is on the plan, the provider set is decided there — mirror its answers instead of asking the client again.
How an engagement starts
This work builds on iOS app foundations & setup, so scope, boundaries and constraints are agreed before anything is built.