Frontend Translation System

Library Used

We use React i18next for handling translations.

---

Current Implementation

• Translations stored in localStorage

• Cached for 24 hours

• On expiry:

  • Cleared
  • Re-fetched

---

Storage Behavior

• Stored per selected language
• Cleared when language changes
• Refreshed after expiration

---

Re-render Behavior

Translations reload on:

• Page refresh
• Component re-render

---

Limitations

• localStorage is disk-based → slower
• Not ideal for large translation sets
• Language persistence issues

---

Proposed Improvement

Move translations to Redux (in-memory storage)

Benefits

• Faster access (RAM-based)
• Better performance on slow systems
• Scalable for future growth

---

Future Enhancement

• Move to sessionStorage in SPA setup
• Fix login language persistence issues