DayTwo Design System
⌘K

Language — Burmese & English

DayTwo ships in Burmese and English, and the two behave differently. Burmese runs longer and stacks taller; words must stay plain in both. Designing for the longer, harder language from the start is what keeps screens working for everyone — not just the English half.

Text expands

The same sentence is about 1.3–1.7× longer in Burmese, and its stacked glyphs need more vertical room. Size every layout for the longer string, never for English.

ENRecord today's cash sale
MYဒီနေ့ ငွေသားအရောင်းကို မှတ်တမ်းတင်ပါ

A primary action shows the effect plainly — the Burmese label is wider, and the button has to hold it without clipping:

Use plain words — in both languages

  • Concrete verbs, not abstractions: "Record sale", not "Submit entry".
  • No accounting jargon in either language — many users don't think in ledger terms.
  • Pair words with clear icons; never rely on an icon alone.
  • Translate the meaning, not the words — a literal translation often reads as stiff or unclear.

Minimise typing

Typing is the most expensive thing we ask of the user, and harder in Burmese script on a small keyboard. Prefer taps, chips, and capture shortcuts (a receipt photo, repeat-last-sale) over free text wherever you can.

Pitfalls

Do
Layout sized for the longer Burmese string and tested in both languages — labels wrap or fit, nothing clips.
Don't
Layout sized to the English label; the Burmese version overflows, truncates, or pushes the action off-screen.
Test in Burmese before calling it done

A screen that looks balanced in English can break in Burmese. Check the Burmese layout — longer strings, taller glyphs, correct font — as part of finishing any screen, not as an afterthought.