Tuesday, April 9, 2019

forms - Edit & save buttons - do I need them? where to place them?


I'm designing a simple app for the Android platform.


I have a page with some data, this page can be reached by two options:



  1. create new page- input fields are empty

  2. edit existing page- input fields are field with data


An explanatory picture could be found here: screenshot


I have two questions:




  1. where to place the edit button or maybe not use an edit button and just enable editing after user presses the field.

  2. where to place the Save button.



Answer



While you may omit Edit button by making the fields editable right away, you have to offer Save, Cancel, Undo, and Redo when allowing users to edit data to provide protection against accidental changes. At the same time, despite having a discrete Save button you may want to keep a "cached" copy of the edits prior to the commit in case the device crashes so that the user can go back to the last uncommitted state.


If you go the way of making the data always editable, you may want to hide the editing controls until the user makes some changes in order to avoid the confusion about the state of the data (i.e. user won't have a visual cue on whether the data has been edited if you show the controls at all times).


The buttons' position depends on how long the page is. If the page is too long (more than 2-3 scrolls), it wouldn't hurt the overall experience to duplicate the buttons on both ends of the page.


In addition, you should pop-up a modal confirmation of saving if the user presses the BACK button after making some changes & not saving them. BACK button on Android must not be treated as a cancellation command because that is not its function by design.


No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...