Users delete information daily. Before you incorporate support for deleting information in your application, think about the type of information that users delete and how essential the information is. On one hand, if users accidentally delete something, they might want the ability to retrieve the information. On the other hand, prompting users to confirm every delete action can slow them down.
You can apply most of the information about deleting to the actions of removing and resetting.
You can use the following table to decide how to incorporate support for deleting information in your application:
|Type of content||Explanation||Examples||Action|
|Not critcal||Users could reproduce the content easily||
||Do not ask users to confirm that they want to delete the item.|
|Moderate||Users could lose valuable application data or content within an application||
Display a toast at the top of the screen that gives users the opportunity to undo the deletion. Once users start to interact with the screen, the toast should disappear after 3 seconds.
If you cannot position the toast at the top of the screen, you could replace the deleted item with the toast.
|Critical||Users could lose valuable data that impacts the device||
Display an inquiry dialog which describes the outcome of the delete action.
This approach makes sure that users are aware of the situation and must explicitly confirm the delete action before it occurs.
You can allow users to delete or remove items in the following ways. Choose the solution that works best for your application.