Expo Better Auth

Implement Better Auth for Expo or React Native with email/password plus Google and Apple sign-in. Keep secrets on the server, use secure session storage on the device, and preserve the project's existing database and navigation choices.

Inspect before changing files

Read package.json, the Expo app config, environment examples, router layout, current API/backend structure, auth files, database schema, and existing sign-in screens. Determine the installed Expo and Better Auth versions and use their matching official documentation.

Do not expose .env contents in output. Do not upgrade Better Auth or Expo unless the user asks.

Choose the backend topology

Better Auth requires a server-side auth instance.

• Expo Router API routes: mount the handler in the Expo app when web/server deployment supports API routes.
• Separate backend: use the existing Node, Hono, Next.js, or other supported server and point the Expo client at its public URL.
• Framework-less React Native: use a separate backend; do not pretend the mobile bundle can safely hold Better Auth server secrets.

Adapt to the existing database adapter. Do not silently introduce a database or ORM.