# Epic / Feature: Social OAuth Login Implementation ## 1. User Story **As a** new or returning mobile app user, **I want to** log in using my Google or Apple account, **So that** I can save time and avoid creating or remembering another password. ## 2. Acceptance Criteria **Scenario 1: Successful Google Login (New User)** - **Given** the user is on the login screen and has not registered before - **When** the user clicks the "Continue with Google" button and authenticates successfully - **Then** a new account is created, the user is logged in, and redirected to the main dashboard **Scenario 2: Successful Apple Login (Returning User)** - **Given** the user has previously created an account using Apple Sign-In - **When** the user clicks "Continue with Apple" and authenticates using FaceID/TouchID - **Then** the system matches the account, logs the user in, and redirects to the main dashboard **Scenario 3: User Cancels Authentication** - **Given** the user clicks a social login button and the third-party prompt appears - **When** the user dismisses or cancels the prompt without authenticating - **Then** the login modal closes, the user remains on the login screen, and a subtle "Login cancelled" toast message is displayed ## 3. Edge Cases & Error Handling - The social provider's API is temporarily down or times out. - The user's Google/Apple account does not have a primary email address associated with it. ## 4. Technical Considerations - Must implement Apple Sign-In to comply with App Store review guidelines if other third-party logins (Google) are used. - JWT tokens must be securely stored in the secure enclave/keychain on the mobile device.