# Cross-platform web support

### Scope <a href="#scope" id="scope"></a>

This document defines how **Personal Account authentication** is supported consistently across **all web platforms**, ensuring the same behavior, security, and user experience regardless of device or operating system.

**In scope:**

* Desktop web browsers
* Mobile web browsers
* Responsive and adaptive UI behavior
* Platform-compatible authentication methods

**Out of scope:**

* Native mobile apps (iOS / Android)
* Desktop applications
* Business / Enterprise account flows

***

### I am new. Where should I start? <a href="#i-am-new.-where-should-i-start" id="i-am-new.-where-should-i-start"></a>

If you are a new user:

* You can access the authentication flow from **any device**
* You do not need to install anything
* The experience adapts automatically to your screen and platform

Just open the web application and begin.

***

### Purpose <a href="#purpose" id="purpose"></a>

Cross-platform web support ensures that:

* Users can sign up and sign in from **any modern browser**
* The authentication experience feels familiar everywhere
* Security behavior remains consistent across platforms
* Users can switch devices without re-learning the flow

***

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

Before using web authentication across platforms, ensure that:

* Your browser is up to date
* JavaScript and cookies are enabled
* You have internet connectivity
* You can access your email for verification and recovery

No platform-specific setup is required.

***

### I already understand. How do I proceed step by step? <a href="#i-already-understand.-how-do-i-proceed-step-by-step" id="i-already-understand.-how-do-i-proceed-step-by-step"></a>

Follow the same authentication flow on any supported device.

***

### 1. Supported Web Platforms <a href="#id-1.-supported-web-platforms" id="id-1.-supported-web-platforms"></a>

#### Desktop Browsers <a href="#desktop-browsers" id="desktop-browsers"></a>

* Chrome
* Safari
* Firefox
* Edge

#### Mobile Browsers <a href="#mobile-browsers" id="mobile-browsers"></a>

* Chrome (Android)
* Safari (iOS)
* Edge Mobile
* Other Chromium-based browsers

***

### 2. Responsive Authentication UI <a href="#id-2.-responsive-authentication-ui" id="id-2.-responsive-authentication-ui"></a>

The authentication UI automatically adapts based on:

* Screen size
* Orientation (portrait / landscape)
* Input method (keyboard, touch)

#### Key UX behaviors: <a href="#key-ux-behaviors" id="key-ux-behaviors"></a>

* Single-column layout on mobile
* Full-width input fields on small screens
* Accessible tap targets
* Optimized keyboard types for email and password fields

***

### 3. Consistent Authentication Behavior <a href="#id-3.-consistent-authentication-behavior" id="id-3.-consistent-authentication-behavior"></a>

Regardless of platform, the following behaviors are identical:

* Unified sign-up and sign-in flow
* Email and password validation rules
* Error messages and helper text
* Email verification process
* Password reset experience

Users see the **same logic**, even if the UI layout changes.

***

### 4. Platform-Compatible Security Methods <a href="#id-4.-platform-compatible-security-methods" id="id-4.-platform-compatible-security-methods"></a>

#### Email Verification <a href="#email-verification" id="email-verification"></a>

* Supported on all platforms
* Verification codes can be entered from any device

#### Email-Based MFA <a href="#email-based-mfa" id="email-based-mfa"></a>

* Works consistently across desktop and mobile browsers

#### Passkeys (When Available) <a href="#passkeys-when-available" id="passkeys-when-available"></a>

* Automatically adapts to device capabilities
* Uses platform-native authenticators when supported
* Gracefully falls back if not supported

***

### 5. Session and State Handling <a href="#id-5.-session-and-state-handling" id="id-5.-session-and-state-handling"></a>

* Authentication state is maintained using secure web sessions
* Sessions persist across page reloads
* Expired or invalid sessions are handled consistently
* Users may be asked to re-authenticate based on security policies

### 6. Device Switching Experience <a href="#id-6.-device-switching-experience" id="id-6.-device-switching-experience"></a>

Users can:

* Start sign-up on one device
* Complete email verification on another device
* Sign in later from any platform without issues

The system does not lock users to a single device.

***

### 7. Accessibility Considerations <a href="#id-7.-accessibility-considerations" id="id-7.-accessibility-considerations"></a>

* Keyboard navigation supported
* Screen reader-friendly labels and messages
* High-contrast UI compatibility
* Clear focus states across platforms

***

### Additional Notes <a href="#additional-notes" id="additional-notes"></a>

* Feature availability depends on browser capabilities, not account type
* Unsupported features degrade gracefully
* Security is never reduced due to platform limitations

***

### Summary <a href="#summary" id="summary"></a>

* One authentication experience across all web platforms
* Responsive UI adapts without changing behavior
* Security and UX remain consistent
* Users can authenticate anytime, anywhere via web


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://oten.gitbook.io/identity-support/user-guide/account-management/user-experience/cross-platform-web-support.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.