·4 min read
MVP Internationalization Tips
Planning to go global? Make smart decisions early that save rewriting later.
Do You Need i18n for MVP?
Usually no. Focus on one market first. But some preparation costs nothing.
Free Preparation Steps
- •Keep all user-facing strings in one file
- •Use a date library that handles locales
- •Store prices in cents, display in local currency
- •Use Unicode for database and inputs
- •Design UI that handles text expansion
When to Add Languages
- •Significant traffic from non-English countries
- •Users asking for their language
- •Targeting a specific market
- •After product-market fit, not before
Currency Considerations
| Approach | Pros | Cons |
|---|---|---|
| Single currency (USD/EUR) | Simple | Friction for some buyers |
| Local currency display | Better UX | More complex pricing |
| Merchant of Record (Paddle) | They handle it | Higher fees |
Translation Options
- •DeepL/Google Translate: Quick first pass
- •Native speakers: Polish the translation
- •Crowdin or Lokalise: Manage translations
- •Do not auto-translate user content
Common i18n Mistakes
- •Hardcoded strings scattered in code
- •Assuming left-to-right text only
- •Fixed-width buttons that break with longer text
- •Date formats without locale handling
- •Images with embedded text
Win one market before trying to win ten. But structure your code so adding languages later is not painful.