Internationalization & Localization — Flutter Course

What you'll learn

Localize copy, plurals, dates, numbers, currency, semantics, and RTL layouts with a maintainable translation workflow. The lesson turns the APIs into a repeatable engineering workflow instead of a collection of isolated snippets.

By the end of this lesson, you'll be able to:

Apply Locales in a production-shaped Flutter feature
Apply ARB resources in a production-shaped Flutter feature
Apply Generated localizations in a production-shaped Flutter feature
Apply Plural and select in a production-shaped Flutter feature

Core mental model

Connect each API to the decision it supports. Flutter code stays maintainable when state, ownership, lifecycle, and platform boundaries are explicit.

Concept	What it means	Decision rule
ARB resource	Structured source messages used to generate typed localizations	Keep user-facing copy out of widget literals
Plural rule	Grammar depends on locale-specific quantity categories	Use localization plural messages instead of appending an s
Directionality	Layout reading direction derives from locale	Use start/end properties and test an RTL locale

Professional workflow

Work in small vertical slices and keep behavior observable from the first iteration.

Define the locale-aware learning summary boundary: user goal, inputs, visible states, ownership, and expected failures.
Build the smallest working vertical slice with typed data and explicit dependencies.
Represent loading, empty, success, and failure behavior where the feature can encounter them.
Verify logic away from the UI, then exercise the rendered behavior at its public boundary.
Inspect lifecycle, accessibility, performance, security, and platform behavior before widening the feature.
Refactor only after behavior is protected by repeatable evidence.

Protect the frame

Keep build methods predictable, move side effects to explicit owners, and measure before introducing caches, isolates, or architectural layers.

Guided Flutter lab

Build a focused locale-aware learning summary slice

This compact example keeps the important ownership and data-flow decisions visible so the behavior is easy to extend and test.

lib/course_summary.dart

class CourseSummary extends StatelessWidget {
  const CourseSummary({super.key, required this.completed, required this.updatedAt});
  final int completed;
  final DateTime updatedAt;

  @override
  Widget build(BuildContext context) {
    final strings = AppLocalizations.of(context)!;
    final locale = Localizations.localeOf(context).toLanguageTag();
    final date = DateFormat.yMMMd(locale).format(updatedAt);
    return ListTile(
      title: Text(strings.completedLessons(completed)),
      subtitle: Text(strings.lastUpdated(date)),
    );
  }
}

Production practice

Contract

Define the locale-aware learning summary inputs, outputs, owner, lifecycle, visible states, and platform assumptions before selecting APIs or packages.

Verification

Protect pure rules with unit tests and the rendered public contract with widget or integration evidence; include one unavailable or failure case.

Operations

Keep dependencies replaceable, log actionable context without user secrets, and measure user-visible behavior before optimizing.

Common failure mode

Concatenating translated fragments assumes English word order and prevents translators from expressing grammar, plurals, and context correctly.

Independent workshop

Extend the guided lab into a review-ready locale-aware learning summary feature that fits the running course portfolio app.

Your finished workshop must include:

Locales
ARB resources
Generated localizations
Plural and select
Dates and numbers
Automated verification and a short design note

Definition of done

Demonstrate the happy path, an empty or unavailable state, and at least one failure path. Add an automated check and a short note explaining one design decision.

Recap & quick check

Key takeaways

ARB resource: Keep user-facing copy out of widget literals
Plural rule: Use localization plural messages instead of appending an s
Directionality: Use start/end properties and test an RTL locale

Quick check

1. Which rule best applies to ARB resource?

2. Which rule best applies to Plural rule?

3. Which rule best applies to Directionality?

Next: Animations & Motion