Responsible use
We explain ideas. We don't hand out other people's code.
Feature Teardowns exists to teach how good software works. Here is where our explanations come from, and the lines we don't cross.
Where our explanations come from
- Open-source apps. Where a feature exists in an app whose code is published openly, we learn from that.
- Public behaviour. What anyone can see by using an app: what it shows, how it responds and what it does over time.
- Lawful analysis. We study software only in ways the law allows, using AI coding agents and REA (Reverse Engineer Anything) to understand how a feature is put together.
What we never do
- We never publish other companies' code.
- We never share private keys, passwords, internal documents or anything else that isn't ours to share.
- We don't explain how to break into accounts, get around payment, or get past an app's security.
What a teardown is
A teardown describes the idea behind a feature in plain English, with a diagram we drew ourselves. The "Build your own" prompt asks an AI coding agent to write a fresh version from that description. Nothing in it is copied from the original app.
What we ask of you
Use these teardowns to learn and to build your own things. Don't use them to clone someone's product, copy their branding, or pass your version off as theirs.