# Forms and Data Entry V1 vs V2 Comparison

V1 provides a basic custom fields capture experience, focused primarily on collecting additional user data — such as name, date of birth, or city — through simple form inputs with limited customization and visual feedback.

V2 redesigns the data entry flow for greater clarity, consistency, and customization — introducing improved field states, enhanced validation feedback, and full alignment with the token-based design system.

<Image align="center" caption="V1 is a basic Forms and data entry experience with limited guidance." src="https://files.readme.io/3ad31fb9b82dbaa009511d228bdd116588d6dee8070541bb324bb5ccf40173be-v1.png" />

<br />

<Image align="center" caption="V2 delivers a more structured, guided, and branded Advanced signature experience." src="https://files.readme.io/9e549de816e984d0ccc82b16f73fbe8d322f5aa6fd480b34e9f02686b2338742-v2.png" />

<br />

***

<br />

## Feature Comparison

Functional capabilities of the module (objective features only; no UX or performance differences).

| Capabilities               | V1 | V2 | Notes                                                                                                                            |
| -------------------------- | -- | -- | -------------------------------------------------------------------------------------------------------------------------------- |
| Forms experience           | ✅  | ✅  | Core functionality present in both versions.                                                                                     |
| Customization options      | ❌  | ✅  | V1 provides limited customization options, while V2 allows full control over text, colors, buttons, illustrations, and behavior. |
| Documentation completeness | ❌  | ✅  | V2 provides complete, standardized documentation coverage.                                                                       |

<br />

***

<br />

## Behavior Differences

How the module behaves during runtime.

| Behavior            | V1                       | V2                                                                | Notes                                                                          |
| ------------------- | ------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| State transitions   | Default transitions      | Specifically designed screen-by-screen transitions for smoothness | V2 includes transition guidelines as part of the module documentation package. |
| Processing behavior | Static processing screen | Branded processing state with consistent loading behavior         | V2 aligns loading behavior with the overall system patterns                    |

<br />

***

## **Customization Overview**

Customization in V2 is significantly simpler and more consistent across modules.

<Image align="center" caption="Customizing the experience to match your brand is simpler in V2" src="https://files.readme.io/0b09856358262acb52de3929eb5d83205aa3888b948467f4b352671578ae1e8e-gif-forms.gif" />

<br />

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.

<br />

<br />