Adversarial Interoperability
Beat a locked-in incumbent by driving the user's switching cost to zero
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 82%
Adversarial interoperability attacks lock-in directly rather than trying to out-feature it. The challenger reverse-engineers the incumbent's file format, feed, or API, then ships a bridge that lets a user operate in the new product while still reading and writing to the old one. This does two things at once: it reduces the switching cost to zero, because nothing is left behind, and it dissolves the collective action problem, because a single person can move without waiting for their friends, colleagues, or customers. Historically this was routine — Apple reverse-engineered Microsoft Office file formats for iWork, Facebook gave new users a bot that pulled their MySpace feed across, and a pair of teenagers reverse-engineered Instagram to strip ads and restore reverse-chronological order. The modern constraint is legal rather than technical: anti-circumvention law, terms-of-service claims, and app-store chokepoints let incumbents remove a bridge within hours.
Origin
Extracted from Masters in Business, where Cory Doctorow traces the tactic through Apple's iWork, Facebook's MySpace importer, and the short-lived OG App.
Core principles
- 01Users do not stay for the product; they stay for what they would lose by leaving.
- 02A better interface is not enough when everyone a user cares about is on the incumbent.
- 03Solve the collective action problem for the user instead of asking them to solve it.
- 04Bridges beat boycotts: let people arrive early without abandoning anyone.
- 05Expect the legal counter-attack to arrive faster than the technical one.
How to run it
- 1
Find the hostage asset
Determine what the user physically cannot take with them: documents in a proprietary format, a following, a purchase history, or a DRM-locked media library.
Pro tip If leaving costs nothing, you do not need this framework — just build a better product.
- 2
Reverse-engineer the interface to that asset
Work out how to read and write the incumbent's format or stream faithfully enough that round-tripping is lossless. Fidelity is the whole product.
Pro tip Perfect read-and-write compatibility is the bar; near-compatibility recreates the switching cost you set out to remove.
Watch out Corrupted or unreliable round-tripping destroys trust faster than having no bridge at all.
- 3
Ship a bridge, not an ultimatum
Let the user live in both places at once — reading the old feed inside the new app, or opening old files in the new suite — so joining requires no sacrifice.
Pro tip Design so the user's existing contacts can join later, at their own pace.
- 4
Strip the extraction, keep the value
Use the bridge to remove what users hate — ads, injected recommendations, algorithmic reordering — while preserving the content they came for.
Pro tip Restoring a simple reverse-chronological feed was enough to reach the top ten on both app stores in a day.
- 5
War-game the legal counter-attack
Assume simultaneous claims for circumvention, tortious interference, computer fraud, copyright, trademark, patent, and trade secrets, plus pressure on whichever gatekeeper distributes you.
Watch out Chokepoint owners will act on a rival's request without waiting for a court; distribution can vanish the same night you launch.
In the wild
In the early 2000s small firms kept a Mac or two but could not reliably read or write Microsoft Office files, so the Mac would eventually be replaced by a PC just for Word, Excel and PowerPoint. Rather than asking Microsoft to fix Office for Mac, Steve Jobs reverse-engineered the Office file formats and shipped Pages, Numbers and Keynote, which read and wrote them perfectly. Doctorow's assessment is that this reduced the switching cost to zero and solved the collective action problem of getting an entire office to move together.
→ Individuals could switch to a Mac alone, keep every file, and let colleagues follow later.
A couple of teenagers reverse-engineered Instagram and built an app that took your login, fetched the queue of content waiting for you, discarded the ads, the recommendations, the boosted posts and the resurfaced clickbait, and showed only the people you followed in reverse chronological order. It was in the top ten on both app stores within twenty-four hours. That same night, Apple and Google removed it at Meta's request.
→ Overwhelming demand proved instantly; distribution was terminated inside a day.
Common mistakes
Competing on features instead of switching costs
A superior interface loses to an inferior network. Nobody sits alone reading better terms of service while waiting for their friends to arrive.
Ignoring the legal surface until launch
The binding constraint is usually anti-circumvention law and terms of service, not engineering. Building first and lawyering later means discovering the ceiling after you have shipped.
Depending on a chokepoint your target controls
If your only distribution is an app store run by the incumbent or its peers, they can end the experiment overnight regardless of user demand.
Is it for you?
Best for
Challengers attacking an entrenched network-effect incumbent where the moat is stored data or social connection.
Not ideal for
Markets where the incumbent's advantage is genuine cost or capability rather than accumulated user lock-in.
From the transcript
“So what he did in economics terms is he reduced the switching costs to zero because you didn't have to leave any of your files…”
“And he solved the collective action problem of convincing everyone to move to a Mac because you didn't have to.”
“was that when Facebook was trying to lure users over from MySpace, it gave them a bot, and you gave that bought your login and…”
From the episode
BONUS: How the Internet Got Worse with Cory Doctorow
Cory Doctorow