Skin deep. You will clone the interface and then meet the wall. Realistically a long weekend.

What stops a copy of Linear working?

The speed is not a feature you add, it is an architecture you commit to. Everything renders from a local store that is already populated, with mutations applied optimistically and reconciled in the background. That means a sync engine: deltas, offline queues, conflict resolution, and a client cache that survives reload. This is the actual product and it is months, not days. Undo across optimistic mutations that have already been broadcast to other clients. Perceived latency is unforgiving. A copy that answers in 200ms instead of 20ms is not slightly worse, it is a different product and people say so immediately.

Can AI copy

Linear

An issue tracker that opens before you have finished pressing the key.

Skin deep

Verdict: Skin deep
Time to copy: a long weekend
Category: ▧ Productivity
Source: Proprietary

The prompt

Written to be pasted straight into an agent with no editing. It describes the whole job, including the parts that will go wrong.

Build an issue tracker that is fast because of its architecture rather than its styling. Client holds a normalised local store hydrated on load and kept current by a delta sync channel; every mutation applies optimistically to the local store, queues for the server, and reconciles on acknowledgement, with rollback on rejection. Support full offline use and a merge strategy for conflicting edits. Model issues, states, labels, cycles, projects and relations. Every action reachable from a command palette, and no interaction may wait on a network round trip before painting. Build the sync engine before any UI; if you build the UI first you will have to throw it away.

Open inClaude ↗Terminal agents take it from the clipboard.

What copies cleanly

The data model. Issues, states, cycles, projects, labels and a board view are a well-trodden schema.
The look, closely. The keyboard palette, the dark surfaces and the tight type are all reproducible.
Keyboard shortcuts, as a list of bindings.

Where it stops

The speed is not a feature you add, it is an architecture you commit to. Everything renders from a local store that is already populated, with mutations applied optimistically and reconciled in the background.
That means a sync engine: deltas, offline queues, conflict resolution, and a client cache that survives reload. This is the actual product and it is months, not days.
Undo across optimistic mutations that have already been broadcast to other clients.
Perceived latency is unforgiving. A copy that answers in 200ms instead of 20ms is not slightly worse, it is a different product and people say so immediately.

What actually protects them

A sync engine that predates the interface everyone admires.
Opinionated defaults that a copy cannot inherit, because the value is in what was left out.
Taste, applied consistently for years, which is not a thing you can specify in a prompt.

Editor's note

The most instructive entry in the productivity category. Everyone copying it copies the visual design, which is the cheap half, and then ships something that feels sluggish and cannot work out why. The answer is that they cloned a photograph of the building.

Somebody already did it

Go and look at the original

We would rather you formed your own opinion than took ours. They built the thing; we only measured it.

linear.app ↗