The site now speaks seven languages
MFKAPPS is now available in English, Turkish, French, Spanish, Japanese, Hindi, and Russian. A short note on why a one-person studio bothered, and how it stays fast.
“For everyone” has been one of the studio’s four rules since day one. It was also, until this week, a bit of a lie — the site only spoke English.
Today that changes. MFKAPPS is now available in seven languages: English, Türkçe, Français, Español, 日本語, हिन्दी, and Русский. You can switch from the globe icon in the header, and every page — home, apps, the blog, even the fine print — follows you into your language.
Why bother, as one person?
Because the apps already crossed borders before the website did. Granyn and Stocky have users who never see a word of English in daily life, and asking them to read a marketing page in a second language to decide whether to trust an app is a small, quiet form of disrespect. The kind this studio is supposed to avoid.
It’s also just correct for the product. If an app promises to be calm and considerate, the first page you land on shouldn’t make you work.
How it stays fast
The easy way to add languages is to reach for a heavy framework and a runtime that ships translation logic to the browser. I didn’t.
Every localized page is still static HTML, generated at build time — one file per language, pre-rendered, zero client-side translation code. The English site is served from the root; each other language lives under its own path (/tr/, /ja/, and so on) with proper hreflang tags so search engines index the right version for the right reader. Switching language is just a normal link to a normal page.
The result: 344 pages across seven languages, and the thing still loads like a single static site — because that’s exactly what it is.
What’s next
The interface and every marketing and product page are fully translated now. The long-form pieces — older blog posts and the legal documents — are being localized next, in the same careful way rather than run through a machine and shipped.
Small studio, same rules. Now in a few more languages.
// Related reading
More from the journal
One App, One Job: Why I Don't Build a Super-App
Every growing app feels pressure to add features and merge into one big platform. Here's why MFKAPPS stays a set of small, single-purpose apps instead.
No Accounts, No Passwords: Why My Apps Don't Have a Login Screen
Six apps, zero sign-up forms. Here's the actual reasoning behind skipping accounts entirely — what it costs, what it removes, and where the line is.
Budgeting with irregular income: a system that doesn't assume a steady paycheck
Most budgeting advice assumes the same amount lands every month. Here's a system built for freelance, commission, or seasonal income that actually holds up.