User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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 picutre 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.
share|improve this question
I <3 inline editing, everybody does. – Naoise Golden Jan 11 '12 at 16:59
Inline editing needs to be discovered and there's no hover state on touch-screens. – dnbrv Jan 11 '12 at 17:09
up vote 2 down vote accepted

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.

share|improve this answer

To be honest I don't think you need either an Edit OR a Save button.

  • For edits - just allow them to edit by selecting the field and starting to type.

  • For saving - I'd suggest just automatically saving by default everytime they complete the field.

You've already determined what the user wants to do on the page by the method they're using to go into it. If they want to edit then you shouldn't require them to choose the 'Edit' button, open the page that needs to be edited and then requiring them to press a different 'Edit' button before they can begin the edits. Keep it simple and clean.

share|improve this answer

The new emerging design pattern is the Done + Discard. If you have a ICS device, just edit a calendar entry, there will be a Done button at the top left, and Discard button at the top right, and they will replace the Action Bar.

enter image description here

Roman Nurik spoke about it here:

There's also code that show how its done:

Its called the done discard pattern.

Specific to your question:

  1. The fields should be editable by default, instead of click-edit-ok.
  2. Save should be called "Done" and placed at the top.
share|improve this answer

Hard to answer, because it depends on what you are doing.

Is the page mainly for editing or mainly for presentation?

I think we could help you more if you post your real screen dump.

If you want to keep it simple, as you write, maybe you can find some inspiration in how the typical android Settings lists present and affords editing of data? See for example the Date and Time settings.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.