UI Copy: Remove vs Delete | The Week of March, 18
Understanding the distinction between "remove" and "delete" is crucial for providing clear and consistent user experiences in software interfaces.
- Definition: "Delete" implies erasure from the system permanently, while "remove" means hiding from the user interface but retaining in the system.
- Examples: Deleting removes information forever, while removing hides it from the user's view but allows for restoration.
- Application: Implement clear language in all components of the application, including buttons, notifications, dialogs, etc.
- Use of "Create" and "Add": Generally, "create" can be associated with "delete," and "add" with "remove."
- Exceptions: Certain items may not conform to this norm, requiring unique labeling.
- Educating Users: Use micro-copy in alerts and empty states to subtly explain the meanings of these actions, promoting user understanding.
This insight is adapted from UI copy: Remove vs Delete by Alex Zlatkus.
Latest from UX Magazine: Stay Updated!
- The Essential Guide to Microcopy and Becoming a More Literate Designer . Explore the art of microcopy and how it shapes user interactions in our insightful article.
- How to Create Storyboards for Design Projects Using Generative AI. Explore how to bring your ideas to life visually without sketching skills.
- Discover the unexpected intimacy of remote work and why the meeting begins long before the meeting begins in the latest episode of Invisible Machines . Join us for an insightful discussion with Gary Sorrentino, Global CIO of Zoom, about the challenges of connecting people in hybrid work environments that are always evolving.