Why we killed the export button

The export button seemed obvious. You snap a board, get a summary, and then want to take that summary somewhere else — Notion, Slack, email, a Google Doc. So in the first beta build, we had an export button that generated a formatted markdown file.

Users clicked it. Then we watched what they did with it.

### What actually happened with exports

The export file went to the Files app. From there, almost nobody opened it again.

This wasn't entirely surprising — Files is a graveyard of well-intentioned exports from dozens of apps — but the specific failure mode was instructive. Users didn't need the file. What they actually needed was one of three specific things:

1. To share the summary as text in Slack — which a copy-to-clipboard button handled better than an export file.
2. To reference the action items later in their task manager — which requires the items to be in the task manager, not in a markdown file in Files.
3. To send the board to a specific person — which a share sheet covered.

The export file covered none of these cases as well as targeted alternatives. It was a general-purpose solution to specific problems, which meant it was a mediocre solution to all of them.

### The hidden cost of the export button

Every feature carries a weight. The export button wasn't just adding capability — it was adding an assumption: that the value of BoardSnap lived in the data it could produce for other apps.

That assumption is partially true. But it was pulling product attention toward being a data exporter rather than being the place where action items live and get worked on.

Every time a user exported their action items to another system, they were also leaving BoardSnap as their action item tracker. The export was a defection mechanism — not because the user was leaving BoardSnap forever, but because the items were now in two places with no sync. The authoritative version was wherever they pasted the export. BoardSnap became the archive.

We made that choice easy for ourselves. We shouldn't have.

### What we shipped instead

Removing export didn't mean locking data in. We replaced it with three targeted actions:

Copy text — one-tap copy of the full summary as plain text. Pastes cleanly into anything. No file management involved.

Share via share sheet — the full iOS share sheet, which handles the dozens of use cases we weren't going to build integrations for.

Copy action items — separate one-tap copy that formats just the action items as a checkbox list. Pastes into Notion, Linear comments, Slack, wherever. The format is common enough to be recognized everywhere.

These three replace 90% of what the export button was doing, without the mental model cost of "I exported this, so now I have to manage a file."

### The deeper lesson

The export button was a hedge. It said: "We're not sure if the value is in BoardSnap or in your other tools, so we'll let you take everything and decide."

That's not confidence. And products that hedge on where value lives tend not to build a very strong case for themselves.

BoardSnap's value is in closing the loop between the board and the action items. The action items should stay in BoardSnap, get worked on in BoardSnap, get marked done in BoardSnap. That's the product.

If there's a specific integration users need — a native Linear connection, a Notion sync, a Jira push — those are worth building. A generic export that dumps everything to a file is not.