I’m building a product that needs localization for push notifications

Got it — push notification localization usually means you need to handle:

• Language selection per user/device
• Localized message content with placeholders
• Fallback behavior when a translation is missing
• Formatting differences like dates, numbers, plurals, and gender
• Platform-specific delivery if you’re using APNs, FCM, or another service

A good approach is to keep notification text as translation keys + parameters, then render the final message in the user’s locale before sending.

Example:

{
  "key": "order_shipped",
  "params": {
    "orderNumber": "12345",
    "eta": "tomorrow"
  }
}

Localized templates:

• en: Your order #{orderNumber} has shipped and will arrive {eta}.
• es: Tu pedido #{orderNumber} ha sido enviado y llegará {eta}.

A few best practices:

1. Use the device/app locale or user preference
2. Store translations centrally
3. Support fallback to a default language
4. Avoid hardcoding text in backend logic
5. Test with long strings and RTL languages

If you want, I can help with any of these next:

• a localization architecture
• a JSON schema for notification templates
• APNs/FCM implementation patterns
• pluralization and variables
• sample code in your backend stack