Building a Bilingual Daily Planner: What I Learned
Building a productivity app in English and Traditional Chinese at the same time sounds like a localization challenge. It is. But it's also something else: a forcing function for clarity.
Let me explain.
The Language Problem Is a Thinking Problem
When you have to explain the same concept in two languages with very different grammatical structures, you discover something uncomfortable: you didn't understand the concept as well as you thought you did.
English lets you be vague. "Get things done" works as a tagline because English tolerates ambiguity. Traditional Chinese doesn't. The language demands specificity. You can't say "get things done" — you have to say what things, for whom, by when.
This sounds like a constraint. It is. But constraints are useful. The vagueness that English lets you get away with is often the same vagueness that makes productivity tools less effective than they could be.
What Bilingual Taught Me About UX
Most productivity apps are designed in English and then "localized" — which usually means translated. The menus get translated. The onboarding gets translated. The error messages get translated.
That's not localization. That's translation.
Real localization starts from a different question: what does a user in Taipei need from this product, on a Tuesday morning, when they're already behind? That answer is not the same as the answer for a user in San Francisco. The context is different. The mental models are different. The relationship to "productivity" as a concept is different.
Building First Light bilingual meant asking those questions early, rather than bolting on a Chinese translation at the end. The result is a product that works naturally in both languages — not a product that works in English with Chinese subtitles.
Three Things I'd Do Differently
1. Start bilingual from day one
Localization at the end is expensive and painful. Localization from the beginning is just design. If you're building for more than one market, make the bilingual decision on day one, not day ninety.
2. Hire for cultural clarity, not just translation
The best Chinese copy for a productivity app is not written by a translator. It's written by someone who understands the productivity culture in that market — what people expect from a morning briefing, what "clarity" means in that context, what a "task" actually is in daily life.
3. Build the English version lean
English has a tendency to bloat. We add features because we can describe them, not because they're useful. Building the Chinese version forces you to ship only what you can explain clearly in both languages — which is usually exactly the right feature set.
Why This Matters for First Light
First Light's Daily Edition ships in two languages simultaneously. Not because it's a nice-to-have — because the clarity that Chinese demands makes the English version better.
If you're building for more than one market, don't think of it as extra work. Think of it as a quality filter.
First Light is live at firstlight.to