String resource names in strings.xml should follow a consistent naming convention to improve maintainability, translation workflow, and overall code readability.
β
Suggested naming convention:
π Examples:
menu_about
title_edit_note
msg_unsaved_changes
btn_save
hint_note_title
dialog_delete_confirmation
π Naming guidelines:
Use lowercase letters and underscores
Avoid camelCase, spaces, or special characters
Structure names by purpose:
title_ β screen titles
btn_ β button text
menu_ β menu items
msg_ β user-facing messages
hint_ β input hints
dialog_ β dialog titles or messages
Optional: Prefix with screen/module name (e.g., editnote_btn_save)
String resource names in strings.xml should follow a consistent naming convention to improve maintainability, translation workflow, and overall code readability.
β Suggested naming convention:
π Examples:
menu_about
title_edit_note
msg_unsaved_changes
btn_save
hint_note_title
dialog_delete_confirmation
π Naming guidelines:
Use lowercase letters and underscores
Avoid camelCase, spaces, or special characters
Structure names by purpose:
title_ β screen titles
btn_ β button text
menu_ β menu items
msg_ β user-facing messages
hint_ β input hints
dialog_ β dialog titles or messages
Optional: Prefix with screen/module name (e.g., editnote_btn_save)