touch-packages team mailing list archive

[Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>]

This morning I came across the headline, "4 iOS Rules to Break", and I
thought, "I bet one of those is putting Cancel/Confirm actions in the
header." Sure enough:

"On iOS, the Done button is often displayed in a navigation bar at the
top of the page. Sometimes the form Submit button (whether called Submit
or something else — for instance, Place Order) is also placed at the top
of the form. This pattern has started to trickle into Android apps as
well. Even in iOS apps we recommend against following this pattern for
the simple reason that it goes against the natural top–bottom workflow
on the page. As users fill in the form, they usually do it top to
bottom. When they get to the end of it, they expect to find a Submit
button right there, next to the last field they have completed. Most of
the time, when people don’t find it there, they get confused and start
looking around, not knowing what to do."
<http://www.nngroup.com/articles/4-ios-rules-break/>

In Ubuntu it's even worse than in iOS, because (a) we use "⟨" to mean
two different things and (b) the "✓" doesn't even have text like it does
in iOS.

I think the rule should be simple: Never put cancel or confirm actions
in the header.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1408015

Title:
  [sdk][UX] Confirmation in the header bar confusing

Status in Quick Memo:
  New
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Imagine a form of some sort, you fill a few fields of data top-down,
  and at the end of it you need to tap in the header at the top to
  save/confirm.

  Pair that with the header going off-screen to leave more screen for
  the content, you have to pull the header in first (and you need to
  know that's where the button will be).

  An example of this behaviour is the calendar app when adding/editing
  an event. One other example (although that could be improved easily by
  auto-saving the new note as soon as it's edited) is the Quick Memo
  app, where when you create a note in the first place you need to tap
  the ✓ icon, but when you're editing, it's all auto-saved and you need
  to tap 〈 to go back to the list of notes.

  I feel like we need to at least come up with clear guidance on what
  belongs in the header, and where a footer with buttons should be used
  (we have a way to stick something on top of the keyboard after all¹).

  http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView
  /#anchorToKeyboard-prop

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Tue Jan  6 17:03:54 2015
  InstallationDate: Installed on 2014-12-17 (20 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/quick-memo/+bug/1408015/+subscriptions