The UI text is written inline in Compose. strings.xml holds about seven entries per app — basically the app name — so the apps can't be translated at all. That's a real barrier for a project meant for families anywhere.
What to do
Take one screen — kid/src/main/java/org/openscreentime/kid/ui/PairingScreen.kt is a good candidate, small and self-contained — and move its user-visible text into kid/src/main/res/values/strings.xml, using stringResource(R.string.…). Use names that describe the meaning (pairing_enter_code_hint), not the text itself.
Deliberately one screen
If this lands cleanly it becomes the pattern for the rest, and the follow-ups can be split among several people. Please don't do all of them in one pull request — it would be unreviewable and would conflict with everything.
Done when
The screen looks identical, no user-visible string is left inline in that file, and the names would make sense to a translator who can't see the app.
The UI text is written inline in Compose.
strings.xmlholds about seven entries per app — basically the app name — so the apps can't be translated at all. That's a real barrier for a project meant for families anywhere.What to do
Take one screen —
kid/src/main/java/org/openscreentime/kid/ui/PairingScreen.ktis a good candidate, small and self-contained — and move its user-visible text intokid/src/main/res/values/strings.xml, usingstringResource(R.string.…). Use names that describe the meaning (pairing_enter_code_hint), not the text itself.Deliberately one screen
If this lands cleanly it becomes the pattern for the rest, and the follow-ups can be split among several people. Please don't do all of them in one pull request — it would be unreviewable and would conflict with everything.
Done when
The screen looks identical, no user-visible string is left inline in that file, and the names would make sense to a translator who can't see the app.