Why the App Store still matters in 2026

I hear the anti-App Store argument constantly. The 30% cut is real money. Review delays can block urgent fixes. Apple's rules are sometimes arbitrary. The web is universal. PWAs are getting better.

All of that is true. And for BoardSnap, I still chose the App Store. Here's why.

### The camera access argument

BoardSnap's core loop — snap a whiteboard with your phone camera — requires native camera access. More specifically, it requires VisionKit, which is iOS-only.

A web app can access the camera. But it can't run VisionKit. It can't get the perspective-corrected, on-device processed image that makes BoardSnap's accuracy what it is. The quality of the scan is the product. That quality lives in VisionKit. VisionKit lives in native iOS.

For a product where the camera is the primary input, "build a web app" is not a real option without fundamentally compromising the product. The App Store is the distribution mechanism for the thing I'm actually building.

### Discovery is real and underrated

The narrative about App Store discovery is mostly negative — "the App Store is a black box, nobody can find your app." This is partially true for general-purpose productivity tools competing in saturated categories.

But it's less true in specific, narrow categories where editorial attention is still worth something. "AI whiteboard" is a real category with real search volume. A user who searches "whiteboard scanner AI" in the App Store is a buyer. The intent is high. The pool of competing results is manageable. App Store search converts at a completely different rate than Google search because the friction to install is near zero — one tap.

In the first month after launch, roughly 35% of new users came from App Store search, not from web traffic or social. That's a channel I'd have had to build from scratch on the web.

### Trust and transactions

BoardSnap has a paid subscription: $9.99/month or $69.99/year. Handling payment on the web means Stripe, customer support for payment failures, building your own subscription management UI.

Handling payment through Apple's in-app purchase means: one-tap subscribe, one-tap cancel, transaction disputes handled by Apple, Family Sharing if the user wants it, and the user's billing info is already on file with a company they trust.

The 30% cut is real. But I'm not writing subscription management code, payment failure retry logic, or dispute handling workflows. For a solo builder, that's a significant amount of work Apple is doing for the price of 30%.

At my current revenue scale, that 30% is more expensive than Stripe would be. At 10x revenue, the arithmetic changes. This is worth watching. But for v1, the tradeoff is real.

### What the App Store gets wrong

Honesty matters here.

App review has blocked a release for three days on an urgent fix. The appeal process is slow. The guidelines are sometimes internally inconsistent — rule X in the Human Interface Guidelines seems to contradict approved patterns from Apple's own apps.

The 30% cut will matter more as revenue grows. I'm already thinking about what a web companion looks like for scenarios where native isn't required — specifically, the ability to view and manage boards on desktop, which doesn't need VisionKit.

And Apple's subscription rules mean I can't offer the aggressive first-month pricing I might want to test. Trial periods are limited to what Apple allows. That's a real constraint on my conversion rate experiments.

### The bottom line

For a camera-first, on-device processing, iPhone-native product: the App Store is still the right call in 2026. The distribution, the trust framework, the payment infrastructure, and the VisionKit access all point the same direction.

For a web-first productivity tool that happens to have a mobile view: build web-first, wrap in a thin native shell if needed, and route around the App Store where you can.

BoardSnap is the first category. The App Store is where it lives.