Phone Number V1 vs V2 Comparison
V1 provides a basic phone number input and verification experience.
While it supports the necessary validation logic, the flow offers less flexibility in adapting the experience to different product needs, markets, or branding requirements.
V2 rethinks the flow to be clearer, and easier to customize, introducing better error handling, and alignment with the token-based system. The V2 experience is designed to reduce user confusion, lower drop-off during verification, and ensure consistent look across platforms and markets.
V1 provides a basic phone number input and verification experience, focused primarily on data submission with limited guidance and flexibility.
V2 provides a more guided and consistent input experience. Improved UX writing and standardized components help users complete the flow with less friction.
Feature Comparison
Functional capabilities of the module (objective features only; no UX or performance differences).
| Capabilities | V1 | V2 | Notes |
|---|---|---|---|
| Phone number verification | ✅ | ✅ | Core functionality present in both versions |
| Inline validation | ✅ | ✅ | Validation logic during entry supported in both versions |
| Error states coverage | ✅ | ✅ | Both handle errors, V2 structures them better and improves clarity |
| Customization options | Limited | Advanced | V2 supports token-based customization |
| Documentation completeness | Basic | Enhanced | V2 provides enhanced, standardized documentation coverage |
Behavior Differences
How the module behaves during runtime.
| Behavior | V1 | V2 | Notes |
|---|---|---|---|
| Error handling | Separate error states, less contextual | Clear, actionable error messages with improved UX writing | V2 reduces cognitive load |
| State transitions | Default transitions | Defined transitions between states | V2 includes transition smoothness and consistency as part of the experience |
| Flow and UI structure | Functional but less standardized | Structured and consistent | Aligned with the tokenized design system |
Customization Overview
Customization in V2 is significantly simpler and more consistent across modules.
Customizing the experience to match your brand is simpler in V2
Instead of having isolated configuration options per screen or component, V2 uses a unified token-based system that allows developers to control visuals, behaviors, and experience patterns with fewer parameters and predictable outcomes.
This means:
- Less engineering work to override UI elements
- Consistent branding across modules
- Predictable behavior when changing settings
- Reduced risk of breaking flows
- Clear separation between visual tokens and experience configuration
V2 also centralizes all customization options under a single structure, so developers always know where to look and what they can modify.