Geolocation V1 vs V2 Comparison
V1 provides a functional geolocation experience that supports the required validation logic. However, the flow is rigid and offers limited flexibility to adapt to different products, markets or branding needs, which can lead to inconsistencies and higher user friction.
V2 redesigns the geolocation flow to be clearer, more flexible and design-system-aligned. Built on a token-based approach, it enables consistent experiences across platforms while allowing customization, helping reduce user confusion and drop-off during verification.
V1 is functional geolocation flow focused on basic location determination.
V2 is a redesigned geolocation experience focused on clarity, flexibility and consistency across platforms.
Feature Comparison
Functional capabilities of the module (objective features only; no UX or performance differences).
| Capabilities | V1 | V2 | Notes |
|---|---|---|---|
| Location detection | ✅ | ✅ | Core geolocation functionality unchanged. |
| Permission handling | ✅ | ✅ | V2 supports configurable permission handling and clearer user messaging. |
| Error States | ✅ | ✅ | Both versions handle common geolocation and permission error scenarios. |
| 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. |
| Flow and UI structure | Functional but less standardized | Structure and consistent | Aligned with the tokenized design system architecture. |
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.