StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>For me, the system-back button should offer the same functionality as the <code>DISCARD</code> button. The <code>DONE</code> button shouldn't be disregarded - it's still common (in apps for mobile or desktop-based) to confirm an action, or actively save/send information in a form.</p> <p>Removing the <code>DONE</code> button as Sporniket suggests means there are two <em>negative</em> interactions (both equating to a cancel) and no confirmation to the user of a save action - for me, I'd be wondering what to do to save the information I'd inputted/changed.</p> <p>Using system-back as the default save action is counter-intuitive; the system-back button navigates backwards through the activity stack - it's associated with an "exit" by common users, not save.</p> <p>If you do decide to continue with your implementation (<code>DISCARD</code> only), then ensure you have some <strong>visual feedback</strong> which allows the user to know that the information has been saved and to help train them (reassure them) that in your app, system-back will save your changes. This could be achieved by using a <code>Crouton</code> when the user presses back, which displays a message telling the user that the data has been saved.</p> <p>-- Edit:</p> <p>I should add that my above recommendations are appropriate where the <code>DISCARD/DONE</code> pattern is appropriate. You mentioned in your question that you're used to changing settings, and pressing back, having it save your changes automatically, and I would suppose that these are areas which are predominantly toggles, rather than content that's being edited.</p> <p>Roman Nurik's post <strong><em><a href="https://plus.google.com/u/0/+RomanNurik/posts/R49wVvcDoEW" rel="nofollow">here</a></em></strong> offers more guidelines, and even mentions a way in which <code>system-back</code> saves information by default. In this instance, he describes having the <code>DONE</code> replace the <code>up</code> affordance, and to hide the <code>DISCARD</code> button in the overflow menu, citing the use-case where the user is unlikely to want to discard information. (IMHO, I disagree with him - I think that if there's a visible <code>DONE</code> or <code>Save</code> action, then <code>system-back</code> should discard, for the reasons stated above. That said, at least it's some guidance for the pattern with usage guidelines from one of the proponents of the pattern.)</p> <p>Overall, I think it's something that could be better answered if you gave more context about the information the user will be editing in this screen.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload