How do I localize push notification content by language?

To localize push notification content by language, the main idea is:

1. Determine the user’s preferred language
2. Store notification text in multiple languages
3. Choose the right language when sending the push
4. Fall back gracefully if a translation isn’t available

Common approaches

1) Localize on the server before sending

Your backend decides which language to use for each user and sends the translated notification text directly.

Example:

• User language = es
• Send: “Tienes una nueva mensaje”

Pros

• Full control over wording
• Works for any push provider

Cons

• More backend logic
• Must maintain translations yourself

---

2) Use device-side localization keys

Instead of sending the full text, send a localization key and let the app display the text using local string files.

This is common for iOS/Android local notifications, and also supported in some push payloads.

Example payload:

{
  "aps": {
    "alert": {
      "loc-key": "NEW_MESSAGE_TITLE",
      "loc-args": ["Alice"]
    }
  }
}

Your app’s localization files contain:

• English: New message from %@
• Spanish: Nuevo mensaje de %@

Pros

• Cleaner push payloads
• Easy app-level localization

Cons

• Usually best for app handling, not always ideal for fully server-rendered push text
• Requires app resources to be bundled and updated

---

3) Store per-language templates in your push service

Maintain templates like:

• en: “You have a new message”
• fr: “Vous avez un nouveau message”
• de: “Sie haben eine neue Nachricht”

Then select the right template based on the user’s locale.

Pros

• Easy to manage at scale
• Works well with push campaign tools

Cons

• Template management can get large

---

Best practices

• Use the user’s app language preference, not just device locale, if they can choose a language in your app.
• Fallback to a default language like English.
• Keep text short, since push notifications have limited space.
• Localize not only text, but also date/time, number formats, and plural forms if needed.
• Test right-to-left languages like Arabic and Hebrew.
• Use language tags like en, en-US, es, fr, pt-BR.

---

Example workflow

1. User signs up and selects fr.
2. Your backend stores preferred_language = fr.
3. A notification event occurs.
4. Backend looks up the French template.
5. Send the French push payload to the push provider.
6. If French is missing, fall back to English.

---

If you’re using APNs or FCM

• APNs supports localized notification keys in payloads via loc-key and loc-args.
• FCM typically sends the text you want displayed, but you can still localize server-side or use app-side localization depending on your architecture.

If you want, I can show you:

• iOS/APNs localization examples
• Android/FCM localization examples
• A backend template system design
• Code samples in your preferred language