string-resources-convention

Name Android strings.xml resources using a structured pattern like `{prefix}_{module_or_context}_{specific_identifier}` with approved prefixes such as `label_`, `title_`, or `action_` to ensure clear maintenance and reliable localization context.

Add POEditor translator comments by inserting an XML comment immediately above each `<string>`, `<plurals>`, and `<string-array>` block in strings.xml to provide translators with intent, variables, and tone.

Format positional placeholders in Android strings.xml using syntax like `%1$s` or `%2$d`, set `formatted="true"` where appropriate, and decide between `getText()` and `getString()` based on formatting needs.

Yes, the Android string naming convention applies when adding, renaming, or reviewing single strings, plurals, and string arrays across different app modules and UI contexts to prevent localization regressions.

Android string resources cause localization regressions when they lack a consistent naming scheme and mandatory translator comments, making it difficult for translators to understand intent, variables, and tone.

Use approved prefixes like `label_`, `title_`, `action_`, and `error_` for Android string resource naming conventions, following the `{prefix}_{module_or_context}_{specific_identifier}` pattern to ensure clear maintenance and discovery.