Answer: loading labels should name work

A frontend answer about naming the current work in loading labels.

For loading labels, I use one rule: name the work, not the desired result. Better sequence: - checking details - saving changes - saved - could not save The risky label is "Saving..." when the app is still validating. It sounds like the write already started. If validation fails, the user feels like the app reversed itself. "Checking details" is less exciting, but more honest. It also gives support threads cleaner language: checking failed, saving failed, or saved but not visible are three different problems.