Partners & OEM demo

A live 3D repair guide, and what it tells you

Below is one of our guides, embedded as it would be on your support page. Use it: every screw you click, every danger zone you open and every step you finish is sent to the page it sits on, as it would be to yours.

Live platform capabilities

Verified today: each can be checked in any guide on the site, and the counts are worked out from the guides when this page is built.

360° screw mappingEvery screw with its length (to 0.1 mm, from repair sources), its drive and its place in the model, colour-coded by length and orbitable in 3D: 407 screws across 68 guides.
Real-time X-ray danger zones with depth alertsThe shell turns see-through on the danger zones: 342 of them, 50 with a maximum pick depth shown on a true-to-scale ruler along the seam.
Zero-plugin WebGLRuns in any browser with WebGL, on phones and computers, with no app or plug-in; without WebGL it falls back to the step stills. The time to the first 3D frame is measured on every visit (player_ready).
1:1 standard step parityEach guide follows the real repair order, and its steps are numbered 1:1 in its JSON spec: 527 steps in all, at /api/teardowns/.
683D guides, each with its own embed
527steps, in the real repair order
407screws mapped by length on the risk maps
342danger zones on the risk maps (no-pry, pick depth, hot or live parts)
194traps to avoid, each played out in 3D
7device categories

Engagement and conversion

Engagement figures (the time readers spend on a guide, the time to the first 3D frame) are published here once enough page views have been measured. None has been yet, so none is shown.

The events, in your analytics

An embedded guide tells the page it sits on what its readers do, through the browser's postMessage. Nothing identifies the reader: no cookie, no stored ID, nothing typed (a random number ties together the events of one page view only).

window.addEventListener('message', e => {
  if (e.data?.source !== 'itakeapart' || e.data.type !== 'event') return;
  const ev = e.data.event; // { event, ts, slug, step, embed_host, ... }
  dataLayer.push({ event: 'itakeapart_' + ev.event, itakeapart: ev });
});

Every guide is also published as structured data: /api/teardowns/index.json lists them, each spec (this one) gives the screws with their lengths and positions, the danger zones, the steps and the part offers, and the JSON Schema describes them.

How a guide is built

  1. The facts. Your service manual, dimensions and fastener lists, or published teardowns and service information for our own guides. If you have CAD exports or scans, we take the measurements from them, so the guide matches your exact revision.
  2. The model and the motion. The device is modelled to its measurements and taken apart in the real order: every screw to its numbered well, every connector in turn.
  3. The risk layer. The danger zones and pick depths, the screw length map and the traps to avoid, each played out in 3D.
  4. Review and publish. You check each step; we publish the guide, its embed and its spec, and update them in place when the product changes.

Talk to us

See For Brands for what a guide shows and the right-to-repair rules, or write to hello@itakeapart.com.

Email us about a pilot