Shareable vehicle profiles

Turn a VIN into a page worth sharing.

The product should decode a VIN, cache the normalized profile, and publish a dedicated car page that feels closer to an official dealership configurator than a database lookup.

Choose one

Visual directions

Tell me A, B, or C in the terminal. These are direction-level choices; the implementation can still borrow details from the others.

A · Recommended

Premium configurator

Hero-first, cinematic, and dealership-like. The car identity leads, then the page unfolds into curated specification groups and confidence details.

Best for the strongest first impression and shareability.
Risk: must keep motion and chrome restrained so the data stays clear.
B

Editorial dossier

Magazine-like and data-rich. It makes the NHTSA decode feel curated, with strong grouping, annotation, and less emphasis on spectacle.

Best for clarity, credibility, and long-form data browsing.
Risk: may feel more like a report than a premium vehicle page.
C

Luxury window sticker

Restrained, artifact-like, and technical. The page feels like a verified document with careful typography, codes, and formal structure.

Best for official-document confidence and minimal visual noise.
Risk: less emotional and less “dealership configurator” than the brief asks for.

Reply with A, B, or C.

After you choose the direction, I’ll write the design spec for the cached VIN profile experience, including architecture, data flow, persistence, error handling, and testing strategy.