2026 • progress log! come back soon

Building Sidi

Sidi is a Chinese reading tool for serious Chinese learners looking to build real fluency by recognizing patterns in the structure of Chinese characters.

Why I’m building this

Cover

16 Feb 2026

back after a bit of a break, during which i procrastinated by building two small tools: a library for all of my markdown artifacts and a reading tracker. making mini tools just for yourself is the most useless and delightful thing.

here’s how i’m phasing out the MVP development (with claude code):

current progress: ✅ phase 0 - 3 complete

12 Jan 2026

MVP has two flows:

There are 5 “levels” of entities that need different treatment.

  1. Compound word (e.g., 电脑): Multi-character word
  2. Composite character (e.g., 明): Built from multiple components
  3. Simple character (e.g., 日): Single semantic unit
  4. Primitive (e.g., 氵): Modifies meaning, rarely stands alone
  5. “Derived” primitive: Variant form of another component

Each level needs a different design treatment. L1 shows word-level breakdown, L2 shows character components, and L3–L5 show etymology and usage.

What I’m working on next:

Previously

Before Jan 9: The manual approach

I started with the idea of building my own dataset, but it seemed high friction and not very sustainable. Building a comprehensive, accurate dataset would take a lot of effort.

Landed on a scoped v0. I would curate 500–700 characters, Simplified Chinese only, 1-2 core user flows, and see how it goes

I also decided on web app over iOS for now to have the lowest possible barrier to iterating / shipping without dealing with app store reviews.

Jan 9: wait, i can just use AI

Realised that instead of curating a static dataset, I could use AI for the character breakdowns. This shifts the entire approach. I can support the full character set from day one and ship much faster.

My thinking on ICP has shifted. Heritage learners were my initial focus, but the opportunity is broader: serious, intermediate learners frustrated with retention and comprehension. The pain point is universal.

I looked at the competitive landscape more closely and did some product teardowns:

Notes for later: I should consider adding stroke order, and spaced repetition flashcards for feature parity, but it's not critical for v0

Considered going mobile again because demand validation is much stronger now, but chose to stick with web to ship faster