Product Facts, Not Fine Print
The download page for a meeting notepad I shipped lists what the app refuses to do — no automatic sharing, no promise of completeness, no substitute for consent — above the download button, in the marketing copy. That placement is the design decision this piece is about.
Nino Chavez
Product Architect at commerce.com
A meeting transcript can be incomplete. Audio drops, a speaker walks away from the microphone, or the model mishears a name. The failure is not that capture has limits. The failure is when the finished note hides them.
Yawn’s download page puts three limits between the feature copy and the installer: No automatic sharing. No promise of completeness. No substitute for consent. The page calls them product facts, not fine print. You scroll through them to reach the download button.
Here’s the claim up front: for a tool whose output is a record, stated limits are not modesty and they are not legal cover. They are part of the product. A record you’ll rely on three weeks from now is only as good as its ability to tell you where it’s thin.
The Confident Note Is the Failure
None of that is a scandal. It is the physics of capture. A fluent summary reads the same whether the capture underneath it was whole or full of holes, and fluency is exactly what generated prose is good at.
Yawn’s answer is structural, not aspirational. Your notes stay separate from generated meeting-note claims. The transcript remains available as the source for checking what happened, rather than being consumed into a summary and discarded. When part of the record is missing or withheld, the app states that plainly instead of smoothing it into a confident note.
The moment that matters is not the meeting. It’s three weeks later, when you reopen the record to check a decision, an owner, a detail. A gap labeled as a gap sends you to a person to ask. A gap papered over with fluent prose sends you into your next meeting holding a quote nobody said.
Only Claims the App Can Confirm
The same rule runs through the smaller surfaces. Recording and transcription state are shown only when the local app can confirm them. The indicator is a report, not a reassurance.
The current release makes the cost of local transcription visible too. The signed 0.5.7 installer is 345 MB. First setup offers a 464 MB Q4 model or a 1.61 GB full Turbo model. The chosen model downloads to the Mac’s private application-support directory; meeting audio never participates in that request.
That distinction matters. The installer is not pretending to be small because the hard part has been moved to a server. The app tells you what is installed, what still needs to come down, and where the meeting data stays. Version, platform, download URL, checksum, and signing evidence travel together instead of being left for the reader to infer.
A Boundary That Costs Nothing Is Copy
Any product page can gesture at restraint. The test for whether a stated limit is a design position rather than marketing texture is simple: did it cost anything?
These limits cost the exact features the category sells. Yawn does not join calls, read a calendar, turn a conversation into a task list, or share a summary on your behalf.
Its sibling app, Cutting Board, holds the same line in a different domain. It proposes a starting order for a day of event footage and stops. It does not edit, decide what is good, identify athletes, or coach players.
The index page that houses them both compresses the position into one sentence: small tools that do one thing and stop where judgment starts.
Analysis narrows what deserves your attention. It does not decide, and it does not act on your behalf. Everything runs on your machine, nothing uploads on its own, and no account is required. Each of those sentences names a feature the category ships and these apps deliberately don’t.
What a Label Cannot Do
Two things stay outside the reach of any sentence on a product page, and the page says so.
The first is consent. The app asks for an explicit check before recording begins, and the page still puts the responsibility where it lives: you remain responsible for getting the consent your meeting requires. A checkbox is a reminder, not a permission.
The last section of the page is not a feature at all. It’s instructions. Use headphones. Be the one person near the microphone. Make the choice clear to the people the recording will capture.
The second is the limits list itself. These are internal alpha builds, and the boundaries are claims under test by real, consented use. The list of what the apps won’t do is expected to grow. When it does, it belongs on the product page in the same type size as the features.
The app can print the sentence about headphones on the screen. Only the person in the chair can make it true.