Dan Tech Academy
After this lesson you will
  • Know where each module's resources live and how the Res class is generated
  • Pick the right stringResource, getString, painterResource, Font or Res.getUri for each need
  • Explain why a missing translation quietly shows English, and use LocaleParityTest to catch it
Duration15 min
DifficultyBeginner

Compose Multiplatform Resources And Localization

Shared resources in Compose Multiplatform: the composeResources folder, each module's Res class, reading strings, images, fonts and files from commonMain, and keeping the Vietnamese version complete with LocaleParityTest.

What this lesson covers
  1. 01Lesson Goal
  2. 02Part 1: From R.string To Res.string
  3. 03Part 2: The composeResources Folders In The Repo
  4. 04Part 3: One Res Class Per Module
  5. 05Part 4: Reading Resources In Code
  6. 06Part 5: Multiple Languages With values-vi
  7. 07Part 6: LocaleParityTest Blocks Silent Bugs
  8. 08Part 7: Drill, Break A Translation
  9. 09Part 8: The Android Packaging Trap
  10. 10Troubleshooting Table
  11. 11Checkpoint
  12. 12Bad Smells
  13. 13References
  14. 14Key Takeaways

Topics: mobile-action-pro, compose-state

14 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: From R.string To Res.string, … — plus 69 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in
Sign in