WitNote · Book Mode Export is part of Hooosberg's public product diary for WitNote. It turns a real build step into a searchable case study for international readers.
WitNote 2.0.1 is a native macOS Markdown writing and knowledge workspace rebuilt in Swift, with local folders, format conversion, bilingual reading, and MLX local AI.
The original Chinese article was published on 2026-06-15 under AI workflow. It focuses on 当笔记变成长文，导出能力就不再是附属功能，而是写作闭环的一部分。
The reusable learning angle is Native Swift macOS, Local AI and MLX, Markdown knowledge workspaces, App Store refactor launch. 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 Native Swift macOS workspace, Markdown folders as a local knowledge base, MLX local AI with a bundled Qwen3 starter model, PDF / Word / EPUB conversion, bilingual reading, and writing assistance. The diary explains how these capabilities are selected, constrained, reviewed, or turned into launch material.
Privacy and trust
User-selected folders, Markdown documents, and exports stay local by default. Local inference does not send writing to a hosted AI service by default; model downloads, StoreKit, and user-opened external links are explicit network actions.
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.