WitNote · Native Calm UI is part of Hooosberg's public product diary for WitNote. It turns a real build step into a searchable case study for international readers.
A Markdown workspace for Mac, iPhone, and iPad (Mac version available now; iPhone and iPad coming with 2.0.6). Notes stay in files you choose, with optional on-device AI. No account, no ads, no tracking.
The original Chinese article was published on 2026-06-16 under Design system. It focuses on AI 写作产品最容易变得吵，WitNote 的 UI 目标是让文字重新成为中心。
The reusable learning angle is Native Swift macOS, On-device AI, Markdown knowledge workspaces, App Store release compliance. The diary format is deliberately practical: context, decision, implementation boundary, review impact, and what another builder can reuse.
This English page is generated from the same public product facts as the Chinese site. It is meant to be indexable and useful now, while still leaving room for later hand-polished translation of the full Chinese narrative.
Context
This entry belongs to the WitNote build series. It should be read as one stage in a larger product journey, not as an isolated announcement.
The site keeps success cases and failure cases together because both create reusable judgment.
Implementation boundary
Relevant product capabilities include Markdown workspace for Mac, iPhone, and iPad, Notes stay in files and folders you choose, Built-in on-device AI for polishing, summaries, and outlines, Open Markdown, Word, PDF, EPUB, and images; export to PDF, Word, HTML, text, and long images. The diary explains how these capabilities are selected, constrained, reviewed, or turned into launch material.
Privacy and trust
No account is required. User-selected folders, Markdown documents, and exports stay in the locations you choose, and the built-in on-device model does not upload documents. If you choose to use optional connected AI where it is available, text is sent to a service of your choice only when you send a request; on Mac, attached document content also requires a separate per-endpoint permission.
For an indie product matrix, trust is built through many small facts: local data boundaries, review status, support links, honest postmortems, and stable canonical pages.
What another builder can reuse
Another builder can reuse the pattern: start with a narrow product promise, make the privacy boundary inspectable, connect every public page to a real download, support path, or source repository when appropriate, and turn the launch process into a searchable article.
That is why the diary sits next to the product page. The product builds trust, and the diary teaches the path that made the product possible.