Challenge
Right-to-left is where most web front ends quietly fall apart. Layout, typography, iconography, navigation direction and form flow all have to reverse, and a product built left-to-right and mirrored afterwards ends up with stray misalignments that a native Arabic reader notices immediately. Chatberry is a conversational product, so the entire interaction is text on screen: any awkwardness in how Arabic sets and flows is not a cosmetic issue, it is felt in the core experience. The brief was a front end that reads as though it was designed in Arabic, because it was built for people who read in Arabic.
Right-to-left is where most web front ends quietly fall apart. Layout, typography, iconography, navigation direction and form flow all have to reverse, and a product built left-to-right and mirrored afterwards ends up with stray misalignments that a native Arabic reader notices immediately. Chatberry is a conversational product, so the entire interaction is text on screen: any awkwardness in how Arabic sets and flows is not a cosmetic issue, it is felt in the core experience. The brief was a front end that reads as though it was designed in Arabic, because it was built for people who read in Arabic.
Solution
We treated right-to-left as a first-class requirement from the first commit rather than as a retrofit. Layout is direction-aware throughout instead of being flipped at the end. Arabic typography was chosen for on-screen reading rather than adapted from a Latin type scale, so line length, weight and spacing suit the script. Navigation, iconography and form flows are composed right-to-left by default. On top of that foundation sits the multi-section home experience that carries the product story, and an authenticated sign-in flow for returning users. Built with Next.js, React and TypeScript.
We treated right-to-left as a first-class requirement from the first commit rather than as a retrofit. Layout is direction-aware throughout instead of being flipped at the end. Arabic typography was chosen for on-screen reading rather than adapted from a Latin type scale, so line length, weight and spacing suit the script. Navigation, iconography and form flows are composed right-to-left by default. On top of that foundation sits the multi-section home experience that carries the product story, and an authenticated sign-in flow for returning users. Built with Next.js, React and TypeScript.
Results
Chatberry has a front end that reads natively in Arabic rather than one that looks translated, which for a text-first conversational product is the difference between a usable product and an awkward one. The site is live and carries both the marketing surface and the authenticated entry point. The engagement also gave techpotions a reusable right-to-left foundation, and it is the concrete work behind the studio's public claim to build comfortably in Arabic.
Chatberry has a front end that reads natively in Arabic rather than one that looks translated, which for a text-first conversational product is the difference between a usable product and an awkward one. The site is live and carries both the marketing surface and the authenticated entry point. The engagement also gave techpotions a reusable right-to-left foundation, and it is the concrete work behind the studio's public claim to build comfortably in Arabic.
