🌍 🌏 🌎

What it Means to...

Scale Your Frontend

🌍 🌏 🌎

Kyle West

Staff Engineer, FamilySearch

© Kyle West

Kyle West

  • Recent Father
  • RS Program Committee Member
  • Staff Engineer at FamilySearch
    • Design System Author
    • Accessibility Lead
  • World Traveler

© Kyle West

"Scale"

© Kyle West

Image Attribution: "Defying Gravity". Blender 3.4, Cycles, 512 Samples, Unsplash License

© Kyle West

es zh ja

Localized Strings

it fr pt

(Level 1)

© Kyle West

Setup Translation Resources

public/locales/en/translation.json:

{
  "welcome": "Welcome, {{name}}!",
  "itemCount":
    "{{count, plural, one {# item} other {# items}}}"
}

public/locales/es/translation.json:

{
  "welcome": "¡Bienvenido, {{name}}!",
  "itemCount": 
    "{{count, plural, one {# artículo} other {# artículos}}}"
}
© Kyle West
import ENGLISH from './locales/en/translation.json'
import SPANISH from './locales/es/translation.json'

i18next.init({
  resources: {
    en: { translation: ENGLISH },
    es: { translation: SPANISH }
  }
  fallbackLng: 'en',
  // ...
});
© Kyle West
import { useTranslation } from 'react-i18next';

export default function Hello({ user }) {
  const { t } = useTranslation()
  return (
    <h1>
      {t('welcome', { name: user.displayName })} 
    </h1>
  )
}
// en: <h1>Welcome, Kyle!</h1>
// es: <h1>¡Bienvenido, Kyle!</h1>
© Kyle West
i18next.init({
  fallbackLng: { 
    'default': ['en'],
    'ua': ['ru'],
    'zh-Hant': ['zh-Hans', 'en'], 
    'de-CH': ['fr', 'it'],
    // ...
  }
});
© Kyle West

import LanguageDetector from 'i18next-browser-languagedetector';

i18next.use(LanguageDetector)
© Kyle West

© Kyle West

Left to Right

Right to Left

(Level 2)

© Kyle West

© Kyle West

© Kyle West

© Kyle West

© Kyle West
Directional Property Logical Property
margin-right margin-inline-end
margin-left margin-inline-start
padding-right padding-inline-end
padding-left padding-inline-start
text-align: right; text-align: end;
text-align: left; text-align: start;
left inset-inline-start
right inset-inline-end
border-right border-inline-end
border-left border-inline-start
border-top-left-radius border-start-start-radius
border-top-right-radius border-start-end-radius
© Kyle West

Other Considerations

  • Consider swapping out images instead of flipping
  • Video & Audio Controls remain LRT
  • Some locales like are "westernizing"
© Kyle West

✌🏾 🟥 🤘🏽

Symbolic Meanings

🟩 🤲🏽 🟦

(Level 3)

© Kyle West

English

Mandarin

MacOS Stocks App

MS Word, Advanced Layout modal for images

🥢 👍🏽

👎🏼 🍴

© Kyle West

iPhone Air Advertisement, Apple.com 2026

🧭 ⬇️ 🧭

The Global South

🧭 ⬇️ 🧭

(Level 4)

© Kyle West

Democratic Republic of the Congo

  • ~117 million, 4th in Africa
  • Avg $1.5 USD daily wage
  • 80% without internet
  • Low technical literacy
© Kyle West

Itel A60

  • ~$50-90 USD
  • 2 GB RAM
  • 32 GB Flash Storage
  • Android 11 or 12 Go
    • ~0.7 GB RAM
    • ~10 GB Storage

Current Users

  • 💻 Multiple devices, per person

  • 🛜 "Unlimited" connection

  • 👩‍💻 Motivated by productivity

  • ⌨️ High Technical Literacy

Emerging Users

  • 📱 Mobile phone only, often shared

  • 📶 Severely limited infrastructure

  • 🎥 Motivated by leisure

  • ☎️ Low Technical Literacy

© Kyle West

Inclusive Solutions Require
🌏 Innovative Change 🌍

© Kyle West

📱 Change Our Culture

  • We must be relentlessly mobile-first
  • Be more deliberate with over-the-wire transactions
  • Design & build products to handle intermittent connection
© Kyle West

🎨 Change Our Designs

  • Borrow design patterns from OS
  • We need to provide clear CTA
  • Resumable tasks
© Kyle West
  • Accessibility (you can look up my React Summit 2025 talk for that)
  • Localizing Dates (the Hijri Calendar will kick your butt)
  • Political Issues (Russia and North Korea)
  • Progressive Web Apps
  • Unicode & Font Subsetting
  • Bundle Optimization & Code splitting
© Kyle West

"Human beings are far more wonderful than machines"

— Fred McFeely Rogers

© Kyle West

Thank you, React Summit!

© Kyle West

Hello everyone! My name is Kyle West, I'm a Web Engineer at FamilySearch. Full disclosure, this talk arose from an argument I had at lunch with a friend. He's a backend engineer, and one day he said something to the effect of: > Well as a UI guy, you don't have to think about things like _scaling_. That might be nice. My friend is a smart guy, but I know that this comment came from decades of backend engineers hating on the frontend. There's a common misconception that "making things look pretty" isn't as complex as the problems backend folk like to solve, but it's entirely false. Frontend folk solve just as complex of problems, if not more so—because UX is full of unsolved problems.

Today I just want to tackle one angle of those kinds of problems: Scaling your application. But what do I mean by "scale". When you hear this word, you might think of: - Load balancing - CDNs - Orchestration Layers - Microservices And this is indeed what the industry tends to think of in terms of scale. But they all follow under the umbrella of "performance" Performance is important to the success of a product. But there is _so much_ more that goes into building a scalable product.

What I am talking about, is a topic with many names. You've probably heard of some or all of these terms, and there's a lot of nuance between each of them, but all of these concepts solve the same general problem: > How do I build something that anyone can use? That's what I want to talk about today. You'll hear me use the term "globalization" to refer to this concept, but just know there are many parts to it.

The first and most obvious problem you'll come across is that not all users around the world speak your language. You'll need to implement a system that lets you swap out the strings in your UI to something the user can read. This use to be a hard problem, but today it's more or less solved.

Now you can just create a JSON file to hold your string values. Notice here that I am using something called the ICU Message Format. It's a little hard to read at first, but it allows us to write some complex interpolation rules. Modern libraries tend to support ICU format.

Where people tend to under optimize, is with choosing an appropriate fallback language. The cheapest option, is just fallback to whatever language the product was originally written in. And that works. It more or less guarantees that a string will show up in any given context. But this is not always the best.

Consider this instead. Your users might prefer something other than your default. Now they can always indicate this with the Browser Settings, but not all will. See here that you can set a list of fallbacks for each locale to be smarter about what is shown when a language is missing for a feature. You might ask, "Why isn't this list standard." That's because it should be a function of what languages you support on your site.

I'm talking about supporting Right-to-Left languages. like: Arabic, Hebrew, Farsi, etc.

One thing that's drastically different from right to left languages, is that their UI should be the mirror opposite of Left to Right layouts. Why is that?

It's because all that work we did during the design phase to get proper balance, grouping, whitespace, etc would be ruined if all we did was have the text right-justified.

See here how the balance changes as we shift the design around towards mirroring. Notice how the second panel feels off ballance. The text feels disconnected from the Avatar and the controls feel over emphasized. Look at the third panel. See how mirroring the UI restores the balance to what the first panel has. We need that for when we render RTL UIs.

The hardest shift is that you need to stop thinking in directional CSS and shift to using logical positioning. Keep in mind that these are just a few of them I felt like calling out. There are plenty more. You can find all of these on MDN if you want to look more into this later.

Confession, this is where I stop being an expert and have become a student. I've been studying this topic a lot recently, but the more I learn, the more I realize that I don't know nearly as much as I want to. I'd like to share with you what I am learning though, if that's ok.

For one, they aren't always online like the others. Not everyone in the world has reliable or strong internet.

Further, may of these people suffer from extreme poverty.

We can't just shoehorn our old solutions (with their accompanying assumptions) into people's lives. We need to adapt our understandings and work culture to meet people where they are at.

MOBILE FIRST - **Discovery** done via mobile - **Design** all experiences for mobile - **Build** & **test** products on limited CPU/memory/storage devices - **Sell-off** experiences on mobile OVER THE WIRE - Monitor & reduce **payload sizes** - Allow users to be in control when actions could (_literally_) cost them - Critical user flows should work with intermittent or offline internet - Need patterns to manage conflicts once online

I'd like to leave you with one of my favorite quotes from Mr Rogers. After this presentation, you might be feeling a little overwhelmed by all the complexity that needs to be maintained to have a global product. When I feel overwhelmed, I think about all the amazing people I've met from all over the world. Everyone is unique, and that means our needs are all unique. But this diversity is what makes life beautiful.

I'm Kyle West. You can find my slides on my website at kylewest.dev/slides It's been a pleasure, Thank so much you! ---------