# Qualified Signature V1 vs V2 Comparison

<br />

V1 delivers a basic Qualified Electronic Signature flow with limited guidance. The experience focuses on completing required steps—reviewing a document, selecting checkboxes, and continuing—without clearly explaining the significance of those actions.

V2 transforms the flow into a guided and trust-centered Qualified Electronic Signature experience. The interface introduces clearer structure and hierarchy, helping users understand what they are agreeing to and why it matters.

<Image align="center" caption="V1 is a basic Qualified signature experience with limited guidance." src="https://files.readme.io/8fefb158ca304b832263786b6c7e93705201b85ebc50a9bdc253503ae4392059-v1.png" />

<br />

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

<br />

***

<br />

## Feature Comparison

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

| Capabilities               | V1 | V2 | Notes                                                                                                                            |
| -------------------------- | -- | -- | -------------------------------------------------------------------------------------------------------------------------------- |
| Signature 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.

<br />

| 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 />

***

<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/11d3ef792b571e1412803317736a640be312cfe2435e0c05716e0aa2ba3f9baf-gifcomparison.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 />