V1 vs V2 Comparison
V1 delivers a basic Advanced 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 Advanced Electronic Signature experience. The interface introduces clearer structure and hierarchy, helping users understand what they are agreeing to and why it matters.
V1 is a basic Advanced signature experience with limited guidance.
V2 delivers a more structured, guided, and branded Advanced signature experience.
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. |
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 |
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.