CURP V1 vs V2 Comparison
V1 provides a basic CURP input and validation experience. While it supports correct data entry and basic validation logic, the flow offers limited flexibility for customization and is not fully aligned with the token-based design system.
V2 builds on the same functional foundation but rethinks the experience to be clearer, more structured, and easier to customize. It introduces standardized components, improved UX writing, better defined validations states and full alignment with the token-based design system.
The V2 experience is designed to improve predictability, reduce friction during validation and ensure consistent behavior.
V1 provides a basic CURP input experience focused primarily on data submission, with limited validation feedback and customization flexibility.
V2 delivers a clearer, structured CURP validation flow with standardized states, improved feedback, and token-based customization support.
Feature Comparison
Functional capabilities of the module (objective features only; no UX or performance differences).
| Capabilities | V1 | V2 | Notes |
|---|---|---|---|
| CURP Validation | ✅ | ✅ | Core validation logic present in both versions |
| Inline validation | ✅ | ✅ | Both support validation during input. |
| 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 | V2 follows standardized layout and spacing rules. |
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.