Li Lance Android Seraphim Framework Flutter Localization

Localization

Priority: P1 (STANDARD)

Consistent multi-language support using easy_localization.

Format Selection

• CSV (Recommended for teams with translators): Google Sheets compatibility via sheet_loader_localization. Store in assets/langs/.
• JSON (Developer-friendly): Nested structure support with IDE validation. Store in assets/translations/.

Structure

# CSV Format (Google Sheets workflow)
assets/langs/langs.csv

# OR JSON Format (nested keys)
assets/translations/
├── en.json
└── vi.json

Implementation Workflow

1. Initialize — Call await EasyLocalization.ensureInitialized() before runApp.
2. Wrap root — Wrap the app with EasyLocalization widget specifying supported locales and path.
3. Translate strings — Use .tr() extension on keys (e.g., 'welcome'.tr()).
4. Switch locale — Change via context.setLocale(Locale('vi')).
5. Handle plurals — Use plural() for quantity-dependent strings.
6. Sync translations — Use sheet_loader_localization to auto-generate CSV/JSON from Google Sheets.

Bootstrap & Usage Examples

See implementation examples for bootstrap setup and translation usage patterns.

Anti-Patterns

• ❌ Hardcoded strings in UI — always use translation keys
• ❌ Using Localizations.of manually — use easy_localization .tr() extension
• ❌ Mismatched keys across locale files — keep keys identical in all locales

Reference & Examples

For setup and Google Sheets automation: See references/REFERENCE.md.

Related Topics

idiomatic-flutter | widgets

Source: li-lance/android-seraphim-framework — distributed by TomeVault.