Architecture NotesGoing Multilingual — Niche Products Deserve a Worldwide Market
00要約Overview
01動機Why
Why localize at all? Solo development is, by its nature, a niche strategy. You survive as an individual precisely by picking up the narrow problems that big companies don't chase. But a niche, viewed inside one country, is too small a market. Even when demand at home is thin, the world as a whole often holds more than enough users. (This "narrow niche × whole world" idea gets its full treatment in 3.1.2 STP.)
And this is the AI era. Translation — that unglamorous, endlessly repeating chore — is exactly where AI shines brightest. The cost of going multilingual has fallen through the floor. Translation quality isn't perfect yet. But for a solo product, being out in the world today is worth far more than a perfect translation someday. If you can do it, there is no reason not to.
02方法How
Three things need localizing: the app's display strings, the store listing, and the screenshots. Each gets its own article: 1.2.1, 1.2.2, 1.2.3.
Two tricks make the road smoother. First: start with two languages. An app built for one language and an app built with plural languages in mind are designed completely differently — but once you support two, the same machinery carries five, or fifty. The step from one to two is the tallest one.
Second: assume AI translation, and preserve context. Hand an AI a bare word and it can't tell what screen it lives on or what it points at — "Home" the house, or Home the first screen? So write down, at design time, what each screen is and what each word means. That habit decides the quality of the whole effort.
03価値What
Localization is not translation work.
It is the mechanism that carries niche value to a worldwide audience.
A niche too small in one language becomes a real market when the world is the denominator. Let AI shoulder the vast, unglamorous translation work, and keep your own hands on design and final review. That is how a solo developer opens the door to a worldwide release.