How Halo Decides
What Not to Build

For every feature that exists in Halo, several others were considered and deliberately left out. The filter for that decision is simpler than it sounds, and it's the same one every time.

The actual question asked

Not "would this be useful in general," but "is this solving a real problem someone is actually having, this week, with an actual pet." A feature that sounds reasonable in the abstract fails this test constantly, because plenty of reasonable-sounding ideas don't map to a genuine, specific need.

What tends to get filtered out

Worth knowing: "no" is the default answer to a new feature idea, not because ideas aren't welcome, but because most software gets worse by accumulating features nobody specifically asked for.

What actually gets built

Features that trace back to a real moment, counting breaths by hand being genuinely difficult, a sitter handover feeling inadequate, a multi-pet household losing track of who's had what. Every existing feature in Halo has an answer to "what specific problem does this solve," and that answer isn't "it would be nice to have."

Fewer features, used on purpose

Everything in Halo earns its place by solving a real, specific problem.

Get Halo
More from the journal
Behind Halo
Why Halo Doesn't Have a Community Feed
Behind Halo
Built by One Person and Her Cat
Behind Halo
Why Halo Started as an iPhone App, Not a Website