Rushi · Localization is part of Hooosberg's public product diary for Rushi. It turns a real build step into a searchable case study for international readers.
Rushi brings together the Diamond Sutra, Heart Sutra, multilingual scripture text, mala counting, quiet sound, and source-backed copybook practice based on open or public-domain source images. Reading and mala features are free; Copy Practice Unlock is an optional one-time in-app purchase handled by Apple StoreKit.
The original Chinese article was published on 2026-05-02 under Product postmortem. It focuses on 多语言宗教文本最重要的是尊重语境，让用户清楚这是阅读辅助而不是解释权威。
The reusable learning angle is Content products, Localization, StoreKit 2, Public-domain source materials, Calm app design. 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 Rushi 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 Diamond Sutra and Heart Sutra, Mala counter, Liu Gongquan and Ouyang Xun copybook sources, Original copybook image preview, iPad support. The diary explains how these capabilities are selected, constrained, reviewed, or turned into launch material.
Privacy and trust
Scripture reading, mala counts, copy-practice works, settings, and copybook practice state stay on device. Rushi has no account system, no ads, and no third-party tracking. The optional one-time Copy Practice Unlock is handled by Apple StoreKit, and Hooosberg does not receive Apple IDs, payment methods, or billing details.
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.