The Report That Earns Its Place on the Genius Bar Counter

Last week I wrote about why Orchard uses SQLite instead of Core Data — specifically, how an append-only time-series workload is a poor fit for Core Data’s object graph model, and how Point-Free’s SQLiteData library gives me the persistence layer and CloudKit sync I need without fighting the data model. That SQLite database is where every monitoring event lands: every app launch, every memory pressure reading, every disk snapshot.

This week I want to talk about what all that accumulated data is actually for — not the upgrade verdict, which I’ve covered before, but a feature I’m probably most excited about in the whole product: the Orchard Report.

The Problem It Solves

Anyone who has been to an Apple Store to buy a new Mac knows the experience. You’re trying to decide between configurations — 16 GB or 24 GB of RAM, 512 GB or 1 TB of storage — and the person helping you is working from guesswork about your actual usage. You’re working from guesswork too. The result is that people either overbuy out of anxiety or underbuy and regret it six months later.

The question “what Mac should I buy?” almost always reduces to “how do I actually use my current Mac?” And almost nobody has a good answer to that, because nothing has ever shown it to them clearly.

After running Orchard for a few weeks, I do.

What the Report Contains

The Orchard Report is a single-page branded PDF generated from the monitoring data already sitting in SQLite — no new collection required. It’s your Mac at a glance: chip generation, RAM, storage, macOS version, your upgrade verdict if applicable, and a plain-English usage summary. Typical concurrent apps. Memory pressure patterns. Disk usage trend. The things that actually determine whether a base-spec machine will suit you or whether you need to step up.

The report exports via share sheet or a dedicated Export button. It’s designed to be printed and handed over.

The Genius Bar Counter Effect

Here is the part that genuinely excites me as a product decision.

Every printed Orchard Report that appears on a Genius Bar counter is a physical advertisement inside Apple’s own retail ecosystem. An Apple Store employee who glances at a well-designed, useful report and thinks “this is exactly what I wish every customer brought” is now an organic recommendation channel. They will mention it to the next customer who comes in without one.

That channel cannot be bought at any price. It can only be earned through report quality and genuine utility to the people reading it. No amount of App Store keyword optimisation or press coverage replicates it. It requires building something worth recommending, which is fortunately the only kind of thing I’m interested in building.

Why This Ships in V1.0

The Orchard Report could easily become a scope trap — there’s always another data point worth including, another layout refinement worth exploring. I’ve avoided that by constraining it tightly: the report only uses data Orchard is already collecting. No new monitoring, no new schema, no new permissions. It’s a read-only view of the SQLite database, rendered as a PDF.

The rough version gets built in Phase 3, during QA and prep, and beta testers will shape the final content. The question I’ll put to them is simple: if you were buying a new Mac tomorrow, what on this report would you hand to the Apple Store employee? If the answer is obvious, it’s working — if not, the content gets simplified until it is. The polished version ships with the App Store submission.

With macOS 27 (“Golden Gate”) now confirmed Apple Silicon only, millions of Intel users face a forced hardware decision in the next twelve months. The Orchard Report gives them data-backed clarity about that decision — a concrete picture of how they actually use their Mac — instead of guesswork at the point of sale. It felt wrong to defer that to V1.1.

If you’re interested in being part of the beta and shaping what ends up on that single page, here’s where to start.

Next up: building a privacy-first sharing system so a family helper can monitor a Mac — without any data touching a server I control.

It launches this fall alongside macOS 27. Follow along at theorchard.app, where you can “Follow the Build” and sign up to be notified about early access this Summer!

Thanks for reading.