The mobile-only positioning bet

"Mobile-first" is a common claim in SaaS and productivity tools. Almost none of them mean it. What they mean is: we have a mobile app, it has feature parity with the desktop, and we designed the mobile version second.

BoardSnap is not mobile-first. It's mobile-only. There is no desktop app. There is no web app. The product exists on iPhone.

This was a deliberate positioning bet. Here's the case for it — and the honest downsides.

### The case for mobile-only

The primary use case happens on mobile. You're standing in front of a whiteboard. You have your phone. You don't have your laptop (or it's in your bag, not in your hand). The capture moment — the moment when BoardSnap adds value — is inherently a mobile moment.

Building a desktop app doesn't serve the capture moment. It might serve the review moment (viewing summaries on a larger screen) or the planning moment (managing your project from a computer). But those are secondary moments. If you optimize for them at the cost of the primary moment, you've gotten the priority wrong.

Mobile-only allows deeper native integration. Every integration decision has to work on iPhone. That means VisionKit, Core Data, the native share sheet, haptic feedback, local notifications, offline queue — all implemented with full native depth, not cross-platform compromises.

Mobile-only is a clearer positioning. When someone asks "what is BoardSnap?" the answer is: it's the iPhone app you use when you're at a whiteboard. That's specific. It's easy to remember. It gives users a clear mental model of when to reach for it.

Compare to: "it's a whiteboard-to-action-plan tool that works on iPhone, Android, and web, with different feature sets on each." Nobody keeps that in their head.

Mobile-only creates scarcity and focus. There are dozens of whiteboard tools. None of them are exclusively mobile with deep native integration. The mobile-only position is uncrowded.

### The downsides

Honesty requires this section.

Team-sharing on a shared screen is awkward. If you want to walk a team through a BoardSnap summary in a meeting, you have to either AirPlay or show your phone. Neither is ideal. A web view of the summary that could be projected would be more natural for this use case.

Some power users want desktop access. I hear this from people who have 50+ boards and want to manage them on a bigger screen with a keyboard. The mobile interface for list management isn't as efficient as a desktop would be.

Android users can't use it. This is the obvious limitation. Android is roughly half the smartphone market. Every Android user who wants BoardSnap is blocked. This is a real cost.

App Store distribution has friction. The web doesn't have a review queue. The App Store does. An urgent fix to a critical bug takes days, not minutes.

### The first month data

In the first month of public availability:

• Zero users mentioned Android (in feedback, reviews, or direct contact) as a blocker to using the app
• Three users mentioned wanting a desktop companion
• Session timing: 84% of sessions happen during working hours (8am–7pm), consistent with meeting use
• Average snaps per active session: 2.3 — suggesting users typically snap multiple boards in a single meeting

The desktop request signal is real and I'm watching it. It's not dominant, but it's consistent. A web view of boards (read-only, sharable) is more likely than a full desktop app — it addresses the sharing-in-a-meeting use case without the full engineering cost of a separate product.

### The bet

The mobile-only bet is: being the best iPhone app for whiteboard capture is more valuable than being an average product across all platforms. If I'm right, BoardSnap becomes the automatic tool — the one you reach for without deciding. If I'm wrong, users default to the camera app on their iPhone and a desktop tool on their computer, and BoardSnap doesn't have a clear home.

Six weeks in, the data suggests the bet is working. I'll have more to say at six months.