0Pricing
Flutter Mobile Development · Leçon

Mises en page RTL et gestion de la direction

Créez des mises en page qui s’inversent correctement pour les langues s’écrivant de droite à gauche avec Directionality.

Mises en page RTL et gestion de la direction est une leçon Flutter Mobile Development gratuite sur CoddyKit. Ceci est la leçon 3 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Flutter Mobile Development, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Flutter Mobile Development comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Why RTL Matters

Languages like Arabic, Hebrew, Persian, and Urdu read right-to-left (RTL). A UI built only for left-to-right (LTR) feels broken to those users: back arrows point the wrong way, text aligns to the wrong edge, and rows appear mirrored.

  • Goal: the entire layout should mirror when the locale is RTL.
  • Flutter handles most of this automatically through a concept called directionality.
  • Your job is to write direction-aware code instead of hard-coding left and right.

In this lesson you will learn how Flutter resolves direction and how to keep your widgets mirroring correctly.

The TextDirection Enum

At the core of RTL support is the TextDirection enum from dart:ui. It has exactly two values: ltr and rtl.

  • Every text-rendering and direction-aware widget needs a TextDirection to lay out.
  • In a real app it is normally derived from the device locale, but it is just a plain enum you can reason about in pure Dart.

Here is a tiny pure-Dart model that mirrors how Flutter picks a start edge from a direction.

enum TextDirection { ltr, rtl }

String startEdge(TextDirection dir) {
  return dir == TextDirection.rtl ? 'right' : 'left';
}

String endEdge(TextDirection dir) {
  return dir == TextDirection.rtl ? 'left' : 'right';
}

void main() {
  for (final dir in TextDirection.values) {
    print('$dir -> start=${startEdge(dir)}, end=${endEdge(dir)}');
  }
}

The Directionality Widget

In Flutter, the ambient text direction is provided by the Directionality widget. It sits high in the tree (usually inside MaterialApp) and exposes a direction to all descendants.

  • Widgets read it with Directionality.of(context).
  • MaterialApp automatically wraps your app in a Directionality based on the current locale.
  • You rarely create one yourself, except in tests or to force a subtree's direction.

Forcing a subtree to RTL is as simple as wrapping it.

Widget buildArabicSection() {
  return Directionality(
    textDirection: TextDirection.rtl,
    child: Row(
      children: const [
        Icon(Icons.star),
        SizedBox(width: 8),
        Text('مرحبا'),
      ],
    ),
  );
}

Start and End, Not Left and Right

The single most important rule for RTL-safe layouts: think in start/end, not left/right.

  • start = leading edge (left in LTR, right in RTL)
  • end = trailing edge (right in LTR, left in RTL)

Flutter gives you direction-aware versions of common APIs that resolve automatically:

  • EdgeInsetsDirectional instead of EdgeInsets
  • AlignmentDirectional instead of Alignment
  • BorderRadiusDirectional instead of BorderRadius

If you use these, your padding and alignment flip automatically when the direction changes.

Widget buildCard() {
  return Container(
    // 16 on the start edge mirrors to the right in RTL automatically
    padding: const EdgeInsetsDirectional.only(
      start: 16,
      end: 8,
      top: 12,
      bottom: 12,
    ),
    alignment: AlignmentDirectional.centerStart,
    child: const Text('Direction-aware padding'),
  );
}

Resolving Directional Insets in Pure Dart

To build intuition, here is how a directional inset resolves to physical left/right depending on direction. Flutter does this internally; modeling it in plain Dart makes the rule concrete.

  • In LTR: start -> left, end -> right.
  • In RTL: start -> right, end -> left.

Run this to see the same logical insets produce mirrored physical insets.

enum TextDirection { ltr, rtl }

class DirectionalInsets {
  final double start;
  final double end;
  const DirectionalInsets(this.start, this.end);

  Map<String, double> resolve(TextDirection dir) {
    if (dir == TextDirection.rtl) {
      return {'left': end, 'right': start};
    }
    return {'left': start, 'right': end};
  }
}

void main() {
  const insets = DirectionalInsets(16, 4);
  print('LTR: ${insets.resolve(TextDirection.ltr)}');
  print('RTL: ${insets.resolve(TextDirection.rtl)}');
}

Rows Mirror Automatically

A plain Row is already direction-aware. Its children are laid out from start to end, so the visual order flips in RTL without any extra code.

  • In LTR a Row of [A, B, C] shows A on the left.
  • In RTL the same Row shows A on the right.

This is why you should let widgets like Row, ListTile, and AppBar do the mirroring for you instead of manually positioning children.

Below, the leading icon and trailing chevron of a ListTile swap sides automatically.

Widget buildSettingsTile() {
  return const ListTile(
    leading: Icon(Icons.person),     // start edge
    title: Text('Profile'),
    trailing: Icon(Icons.chevron_right), // end edge
  );
}

Direction-Aware Icons

Some icons are inherently directional: back arrows, chevrons, and the send arrow should point toward the end of the reading direction.

  • Material provides mirrored variants, e.g. Icons.arrow_back has Icons.arrow_back_ios and the auto-mirroring Icons.arrow_back behaves well in BackButton.
  • For custom directional icons, wrap them so they flip in RTL using Transform.flip based on the resolved direction.

Reading the ambient direction lets you decide whether to mirror.

Widget buildSendIcon(BuildContext context) {
  final isRtl = Directionality.of(context) == TextDirection.rtl;
  return Transform(
    alignment: Alignment.center,
    transform: isRtl
        ? Matrix4.rotationY(3.1415926) // flip horizontally
        : Matrix4.identity(),
    child: const Icon(Icons.send),
  );
}

Text Alignment Follows Direction

For text, prefer TextAlign.start and TextAlign.end over TextAlign.left and TextAlign.right.

  • TextAlign.start aligns to the left in LTR and to the right in RTL.
  • A single mixed-direction string (Arabic with embedded English) is handled by the text engine's bidi algorithm, but the paragraph's base direction comes from the ambient Directionality.

Using start means your form labels and body text align to the correct edge in every locale.

Widget buildLabel() {
  return const Text(
    'Email address',
    textAlign: TextAlign.start, // mirrors with direction
    style: TextStyle(fontSize: 16),
  );
}

Testing Both Directions

The cleanest way to verify mirroring is to render the same subtree twice under each direction. Wrapping a widget in Directionality overrides the ambient value for that subtree only.

  • Great for widget tests and for a debug preview screen.
  • You can also flip the whole app by setting locale to an RTL locale like Locale('ar').

This helper builds an RTL preview of any child.

Widget rtlPreview(Widget child) {
  return Directionality(
    textDirection: TextDirection.rtl,
    child: child,
  );
}

Widget buildPreviewRow(Widget child) {
  return Row(
    children: [
      Expanded(child: child),                 // ambient direction
      Expanded(child: rtlPreview(child)),     // forced RTL
    ],
  );
}

Common RTL Mistakes

Most RTL bugs come from hard-coded sides. Watch for these:

  • EdgeInsets.only(left: 16) stays on the left even in RTL. Use EdgeInsetsDirectional.only(start: 16).
  • Alignment.centerLeft does not flip. Use AlignmentDirectional.centerStart.
  • Positioned(left: 0) in a Stack does not mirror. Use PositionedDirectional(start: 0).
  • Hard-coded TextAlign.left for body text.

Rule of thumb: if an API has a Directional sibling, prefer it.

// Mirrors correctly in RTL:
Widget buildBadge() {
  return Stack(
    children: const [
      Placeholder(),
      PositionedDirectional(
        top: 4,
        start: 4, // right side in RTL
        child: Icon(Icons.new_releases),
      ),
    ],
  );
}

Reading Direction in Logic

Sometimes your business logic needs the direction too, for example to choose a swipe gesture or an animation slide offset. Read it once and branch on a clean enum.

  • Compute a sign: +1 for LTR, -1 for RTL, then multiply offsets.
  • Keep this logic pure so it is easy to unit test.

This pure-Dart helper shows the pattern you would call with the resolved direction from Directionality.of(context).

enum TextDirection { ltr, rtl }

double slideOffset(TextDirection dir, double distance) {
  final sign = dir == TextDirection.rtl ? -1.0 : 1.0;
  return sign * distance;
}

void main() {
  const distance = 120.0;
  print('LTR slide: ${slideOffset(TextDirection.ltr, distance)}');
  print('RTL slide: ${slideOffset(TextDirection.rtl, distance)}');
}

Quick Check

You need a left padding in LTR that becomes right padding in RTL, automatically.

Recap

You learned how Flutter handles right-to-left layouts:

  • TextDirection (ltr/rtl) drives everything; Directionality provides it to the tree, and Directionality.of(context) reads it.
  • Think in start/end, not left/right. Prefer EdgeInsetsDirectional, AlignmentDirectional, BorderRadiusDirectional, and PositionedDirectional.
  • Row, ListTile, and most Material widgets mirror automatically; let them.
  • Use TextAlign.start for text, and mirror inherently directional custom icons.
  • Verify by wrapping subtrees in a forced Directionality or running under an RTL locale like Locale('ar').

Avoid hard-coded sides and your UI will feel native to RTL users with almost no extra work.

Questions Fréquemment Posées

La leçon « Mises en page RTL et gestion de la direction » est-elle gratuite ?

Oui — le texte complet de « Mises en page RTL et gestion de la direction » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Flutter Mobile Development, passe à CoddyKit PRO. Le cours Flutter Mobile Development comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Mises en page RTL et gestion de la direction » ?

Créez des mises en page qui s’inversent correctement pour les langues s’écrivant de droite à gauche avec Directionality. Tu pratiques Flutter Mobile Development avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Flutter Mobile Development ?

Aucune expérience préalable n'est requise. Flutter Mobile Development sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 3 sur 4.

Combien de temps prend la leçon « Mises en page RTL et gestion de la direction » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Flutter Mobile Development ?

Oui. Chaque leçon Flutter Mobile Development inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Fichiers ARB et processus de localisation avec gen_l10n
  2. Pluriels, genre et formatage des messages ICU
  3. Mises en page RTL et gestion de la direction
  4. Sémantique, lecteurs d’écran et composants accessibles
← Retour à Flutter Mobile Development