Summary
As HaloPay expands into LATAM and Francophone Africa, English-only interfaces are a hard blocker for adoption. The codebase currently has dozens of hardcoded English strings scattered across React components, making localization impossible.
We need to architect a robust internationalization layer using next-intl. This requires extracting every user-facing string into structured JSON dictionaries. The architecture must support dynamic locale routing, allow the merchant to switch languages seamlessly via the settings modal, and automatically detect the device's native language preference on first boot.
Acceptance Criteria
Tech Stack
Next.js 14, next-intl, React.
Summary
As HaloPay expands into LATAM and Francophone Africa, English-only interfaces are a hard blocker for adoption. The codebase currently has dozens of hardcoded English strings scattered across React components, making localization impossible.
We need to architect a robust internationalization layer using
next-intl. This requires extracting every user-facing string into structured JSON dictionaries. The architecture must support dynamic locale routing, allow the merchant to switch languages seamlessly via the settings modal, and automatically detect the device's native language preference on first boot.Acceptance Criteria
next-intland configure locale routing.en.json,es.json, andfr.json.Tech Stack
Next.js 14,
next-intl, React.