FAQ

more FAQ

Q: What is your recommended Japanese fonts?

A: This is a crucial point for great UX! Even with perfect translation, using the wrong font can make an app look "unnatural" to Japanese users.

• For System Apps (Recommended): I recommend using system fonts. On iOS, it's Hiragino Sans, and on Android/Web, it's Noto Sans JP. This ensures your app looks like a first-class citizen on the device.

• For Modern/Web Apps: Noto Sans JP (via Google Fonts) is the gold standard. It's clean, professional, and highly readable.

• For Minimalist Designs: Inter combined with Hiragino Kaku Gothic or Noto Sans JP creates a very modern, polished feel.

Avoid using "default" fonts that might fallback to Chinese (Ming/Mincho) styles, as some characters can look slightly different and strange to Japanese eyes. If you're unsure about your font settings, feel free to ask during our collaboration!

Q: How do you handle technical terms or app-specific jargon?

A: Good question! I always cross-reference with your app’s context. If a term is standard in the Japanese dev community (like "Deploy" or "Build"), I’ll keep it or use the katakana equivalent that feels most natural. If I’m unsure about a specific term in your niche, I’ll reach out to you to ensure we’re on the same page.

Q: Can I request small updates for new features later on?

A: Absolutely! I’d love to support your app’s growth. For minor text additions (like a few new buttons or strings), we can discuss a custom micro-plan. My goal is to maintain a long-term relationship with indie devs, so don't worry about having to buy a full package for every small update.

Q: What if a translation feels slightly off after I implement it?

A: Sometimes a word looks different once it’s actually in the UI. If you find a string that overlaps a button or feels "too long" in the actual app layout, let me know! I offer free minor adjustments within 5 days of delivery to make sure the UI looks perfect.

Q: Should I provide screenshots of my app?

A: It’s highly recommended! Japanese is a high-context language. Knowing whether a word is a "Title," a "Button," or a "Tooltip" helps me choose the right level of politeness and word length. A simple Figma link or a few screenshots can dramatically improve the final quality.

Q: Why not just use GPT-4 or DeepL?

A: AI is great at grammar but struggles with "UX writing." For example, an AI might translate "Submit" into a very formal Japanese word that sounds like a government form. I choose words that make users want to click—considering the vibe of your app and the habits of Japanese users.

Q: Will my code placeholders (like {name} or %s) stay safe?

A: Of course. I have a background in development, so I understand that variables like {{user}}, %d, or $amount are functional code, not just text. I will ensure they are placed in the grammatically correct position in Japanese without breaking the logic.

Providing a list of your placeholders' meanings helps me translate more accurately!

Q: How do you handle English pluralization (e.g., "1 item" vs "2 items")?

A: Japanese doesn't have plural forms like English does. I will translate these strings to sound natural in all cases, often using inclusive phrasing that works for both singular and plural. If your framework uses complex plural logic (like i18next plurals), I can handle that too.

Q: What if the Japanese text breaks my UI layout?

A: Japanese characters (Kanji) tend to be wider than Latin letters, while sentences are often shorter. If a translated string is too long for a specific button or header, I can provide a "short version" or a creative alternative to make sure it fits beautifully within your UI.