The staple app strategy

There are two kinds of apps on your phone. Apps you decide to open, and apps you automatically open.

Decide-to-open apps compete for attention every day. They need good notifications, good content, good reasons to return. They are always one new competitor away from losing that attention.

Automatic apps are staples. You open them without deciding. They're attached to a behavior, not a content feed. Gmail when an email needs sending. Maps when you need directions. Camera when you see something worth capturing.

The homepage of BoardSnap literally says: "Built to be the staple AI whiteboard app." That's a positioning claim, but more importantly, it's a product strategy. Here's what that strategy requires.

### Staples are attached to behaviors, not features

The first trap in app building is feature competition: "our app has more features than theirs." Feature competition produces apps that are useful but not staples. Users evaluate them, compare them, and might switch if the competitor ships a better feature.

Staples don't work like that. You don't evaluate Maps every morning. You open it when you need directions. The behavior triggers the app. The app executes the behavior. That's the loop.

For BoardSnap, the target behavior is: when a meeting or session ends and there's a whiteboard in the room, you snap the board. That's the behavior. BoardSnap is the app that executes it.

The question isn't "does BoardSnap have better features than the alternative?" The question is: "is snapping the board with BoardSnap the automatic thing I do when I'm standing in front of a whiteboard?"

### Staples are friction-free

Any app that requires you to think about the app is not a staple. Staples disappear into the behavior.

This is why I've obsessed over the time-to-snap metric. From the moment a user decides to snap a board to the moment the board is snapped: how many taps? How much friction? How long does it take?

In BoardSnap, the answer is: one tap to open, one tap to start the scanner, one tap to shoot. Three taps, under five seconds. If you're in the right project already, two taps.

Every additional second, every additional tap, every additional decision point is a threat to the staple behavior. The friction is the competitor.

### Staples have a clear first-use moment

Staples usually have a single, specific moment where the behavior clicks in. For Maps, it was the first time you were lost and Maps got you un-lost. For Camera, it was the first photo you were glad you took.

For BoardSnap, the first-use moment is the first snap that actually saves you something. The first time you snap a board and get back a clean action list — and you realize you would have spent twenty minutes retyping that by hand — is the moment the staple installs.

Everything about onboarding and first-use is in service of getting to that moment. The first snap needs to be genuinely useful. A demo board, a tutorial board, a test board — none of those install the staple. The first snap from a real meeting that produces a real output: that's the one.

### Staples tolerate imperfection better than feature apps

Here's an interesting asymmetry. If a feature app makes a mistake, you evaluate it — "is this still the best app for this job?" If a staple makes a mistake, you correct it and move on.

This isn't an excuse to ship bad AI output. It's an observation about the stakes. If BoardSnap misreads one item on a board, the behavior-attached user corrects it and keeps going. The relationship is with the behavior, not with any individual output.

Building for habit means building for the relationship over time, not for perfection on any single interaction.

### The honest cost

Building a staple takes longer than building a feature app. You have to wait for the habit to form. Early retention numbers will look worse than they feel, because some users are building the habit and some aren't yet. You have to optimize for habit formation before you can measure it accurately.

BoardSnap is early. The staple is installing for some users and not others. That gap is the work of the next six months.