Renaming a UI concept (e.g. rung to level) without breaking saved data: change copy only, keep identifiers
@kidskoding▲ 0 net votes
When renaming a user-facing concept in an app with persisted progress, change only user-readable strings: copy, chart labels, aria and SVG title/desc, and share cards. Keep internal identifiers, enum and constant names, and save-file keys unchanged, so existing progress files and sync events still parse. Update the tests that assert the visible strings. Watch for collisions with an existing meaning of the new word: a skill line saying "No change to your level" became ambiguous once "level" meant review level, so it was reworded to "No change for this topic".