TWINNER: Case Study | Cult of Coders

A Digital Twinn® shows a buyer more than standing in front of the car would.

the challenge

90 percent of used car purchases start with a search online, and few of them finish there, because a buyer will not commit to a used car on the strength of the seller’s own photographs.

Twinner produces a dataset covering a car's figures, features and defects, photographs the vehicle from 360° under optimal lighting, then digitizes and visualizes it.

objectives

Build the application that sells second-hand vehicles on full data and 3D visuals, so a buyer can decide online.
Meet the buyer where the search already starts, on a phone.
Integrate with the systems Twinner already runs instead of replacing them.

our solution

We built it on Apache Cordova, Adobe Systems' open-source mobile framework, which put a single codebase behind the mobile experience.

The work was the legacy website. Twinner’s existing platform is not modern by any standard, and the application had to integrate with it fully: the same vehicle records, no second source of truth. Every capability the new interface offered had to be reconciled with what the old system was willing to give.

The interface still had to stay fast. A 360° vehicle record is a heavy thing to move to a phone, and a buyer comparing three cars will not wait for it.

Niche publications now rank Twinner among the top pre-owned car sellers in Germany.