Why Preview exists

Arity sells one of the richest mobility-data platforms in the U.S., but enterprise sales decks are a poor way to demonstrate what real driving data feels like. Preview is the answer: a live, activation-coded app that puts driving data, crash detection, predictive routes, and safety insights in a prospective partner’s hand — using their own trips, not canned demos.

It exists for a B2B audience: business leaders, marketers, and product strategists evaluating whether to integrate Arity’s APIs into their own mobile experiences.

I owned UX for the product end-to-end: discovery, onboarding, the showcase modules themselves, and the v1.2.0 redesign that simplified the entire flow.

What I owned

• Discovery and stakeholder interviews with Arity’s enterprise sales and partnerships teams
• The activation-code onboarding — a deliberately short path from “got the code” to “seeing your own data”
• IA for the showcase modules: Driving Data, Crash Detection, Driver Safety, Predictive Routes
• The v1.2.0 redesign — fewer steps to the core experience, data front and center
• Component contributions to the Arity mobile pattern library used by adjacent product teams

Process

1. Reframe the audience

Early prototypes treated Preview like a consumer driving app. It isn’t. The user is a partner-side decision-maker who has 90 seconds to feel “oh — this could plug into our app.” Once we reframed the audience, the entire structure simplified: less coaching, more capability, more honest data.

2. Strip the onboarding

Pre-redesign, getting from activation code to the first interesting screen took too many steps. The v1.2.0 release notes describe the result publicly: “With fewer steps you will reach the core experience quickly without losing clarity.”

3. Put data front and center

The redesigned interface leads with the data that matters — driving signals, crash events, predictive route insights — instead of burying it behind explanatory chrome. Public release notes for v1.2.0: “Redesigned Interface: Data is now front and center, making it easier to understand the power of Arity.”

4. Contribute components upstream

Every component built for Preview was authored against the Arity mobile pattern library so sibling product teams (Routely, partner integrations) could reuse them on day one.

Outcomes

• Shipped on the App Store and currently live at v1.3.0 (March 2026 release)
• The v1.2.0 redesign cut steps to the core experience and reframed the interface around the data itself
• Components contributed back to the mobile pattern library are now reused across multiple Arity products
• Preview is now a default tool in the Arity sales motion — partners experience the platform instead of just hearing about it

Reflection

Preview was the case that proved the brand’s “Perceptive Advisor” voice could become product UX, not just marketing — even for a sales-tool audience. The next iteration is about deeper personalization of the showcase modules so each partner sees the slice of Arity’s capabilities most relevant to their own use case.

Note: production screens and engineering specs for this case study are protected. The full unredacted walkthrough is available on request — but the live experience itself is on the App Store.