Facebook Language Settings
Reimagining how billions of people around the world set, manage, and navigate their Facebook language experience — supporting hundreds of languages and complex script systems.
Facebook as a Global Product
Facebook is used in over 100 languages, by people who switch between multiple languages daily, who live in multilingual households, who type in scripts that read right-to-left or require different input methods entirely. The language settings experience is where all of that complexity meets the user — and for most of Facebook's history, those settings hadn't kept up.
My Role
Lead designer on this initiative, working within Meta's Global Experiences team — closely with internationalization engineers, content strategists, and localization specialists.
A Settings Experience That Didn't Reflect Reality
The existing language settings were built on a model that assumed users had one primary language. In reality, hundreds of millions of Facebook users are multilingual — they communicate in different languages with different people, consume content in multiple languages, and expect a platform to understand that complexity.
What Users Were Experiencing
- Difficulty finding and changing language settings — the surface was buried and inconsistent across platforms
- No way to express multilingual identity or set preferences across languages
- Poor handling of script-specific needs — right-to-left languages, complex scripts, and mixed-script inputs all had edge cases the design didn't account for
- No mechanism for users to flag translation errors
The Design Question
How do we design a language settings experience that's simple for monolingual users, powerful for multilingual ones, and culturally appropriate for billions of people across hundreds of languages?
Research Across Markets
Designing for language at global scale requires humility. Most design teams (and most designers) are monolingual English speakers working on products that assume English as a default. Getting this right meant genuine immersion in how multilingual users actually experience the product.
I worked with the research team to conduct studies across multiple markets — specifically recruiting multilingual users in markets with the highest language complexity. What we found reframed the design problem: users didn't think of "language settings" as a discrete feature. They thought about it as part of their identity and their communication patterns.
Design Principles
Monolingual users shouldn't have to navigate complexity. But multilingual users should be able to express the full range of their linguistic identity.
For multilingual users, how they use language is deeply personal. The design should feel expressive, not bureaucratic.
In global design, the "edge case" is often the majority case in a different market. RTL support, complex scripts, and mixed-language content aren't exceptions — they're the product.
Key Design Work
Multilingual Profile & Settings
I redesigned the language settings surface to support multiple languages — giving users the ability to set primary and secondary languages, manage translation preferences, and control how their profile appeared to speakers of different languages. The challenge was making this feel intuitive for users who'd never thought about it, while being genuinely useful for users who thought about it constantly.
Script & Input Complexity
Languages like Arabic, Hebrew, Thai, and Hindi have fundamentally different rendering requirements. I worked closely with internationalization engineers to understand the constraints, then designed interfaces that handled bidirectional text, script-specific input patterns, and mixed-script content gracefully — not as afterthoughts, but as first-class design considerations.
Impact at Scale
Changes to Facebook's core settings surfaces reach billions of users. The redesigned language settings improved completion rates for language setup and reduced support contacts related to language confusion.
More importantly, it established design patterns for multilingual identity that influenced how Meta thought about the problem across other products. The framework we built for handling language complexity became a reference point for later work in Global Experiences.
The most important design decisions are often the ones about defaults: what does the product assume, who does it center, and who gets treated as the edge case?
"There are 4 billion people on Meta's platforms. Most of them aren't native English speakers. Designing like they are is a choice — and not a good one."