[sdk] Haptic feedback (vibration) is inconsistent between UI elements

[Michael Hall]

Having haptic feedback on the dash is great! However, having it for normal tap activation isn't. Normal activation of dash elements is usually instant, so no additional feedback is required.

Currently these elements have instant haptic feedback:
- apps in the Dash
- keyboard buttons (by default)
- System Settings categories
- page stack items
- pushbuttons (e.g. in the power dialog)
- checkboxes (e.g. in Language & Text settings)
- switches
- Browser toolbar buttons, except for Add Bookmark

These do not:
- apps in the Launcher
- unlock screen and phone dialpad buttons
- toolbar buttons everywhere except Browser
- links in Web pages
- pushbuttons or checkboxes in Web pages
- text fields anywhere

One way to resolve this inconsistency would be to reserve haptic feedback for long-press. The user often doesn't know if it's been triggered or not. Having vibration happen when long-press is recognized might be the best use of this feature.

*** UX Solution ***
We agree with the above solution. Haptic feedback should be reserved for long press & keyboard buttons (on by default).
All the other elements should not have haptic feedback.

[Jamie Strandboge (jdstrand)]

I'll toss in my own feedback on the feedback: app launch is not instant, so it seems to make sense there (for now). App to the foreground (ie, from Recent Apps) is instant, and doesn't seem to need haptic feedback.

[Michał Sawicz (saviq)]

Neither are controlled by unity8 at the moment.

By tvoss' direction, filing this against UITK.

[Jouni Helminen (jounihelminen)]

Agreed vibration should happen only on long press. Timp can you have a look at this?

[Florian Boucault (fboucault)]

On Android it happens on normal press by default I believe with an option
in the settings to turn it off.
On Sep 2, 2014 10:01 AM, "Jouni Helminen" <email address hidden>
wrote:

> Agreed vibration should happen only on long press. Timp can you have a
> look at this?
>
> ** Changed in: ubuntu-ui-toolkit
> Importance: Undecided => High
>
> ** Changed in: ubuntu-ui-toolkit
> Assignee: (unassigned) => Tim Peeters (tpeeters)
>
> ** Changed in: ubuntu-ux
> Status: Triaged => Fix Committed
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> UI Toolkit.
> https://bugs.launchpad.net/bugs/1267592
>
> Title:
> [sdk] Vibrate should happen on long-press, not normal activation
>
> Status in Ubuntu UI Toolkit:
> New
> Status in Ubuntu UX bugs:
> Fix Committed
>
> Bug description:
> Having haptic feedback on the dash is great! However, having it for
> normal tap activation isn't. Normal activation of dash elements is
> usually instant, so no additional feedback is required. Long-press,
> however, is different and the user often doesn't know if it's been
> triggered or not. Having vibration happen when long-press is
> recognized would be the best use of this feature.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1267592/+subscriptions
>

[Tim Peeters (tpeeters)]

On N9 you get haptic feedback on each (short) press and it works quite nice

[Tim Peeters (tpeeters)]

A setting to switch it off makes sense, but in general I think it is helpful to get feedback that a press was detected. As Jamie said, app launch is not instant, and probably there are more things not instant. Some components like Buttons have visual feedback but they may be hidden by the button pressing them.

[Matthew Paul Thomas (mpt)]

It's weird that checkboxes and switches have haptic feedback when tapped, but buttons, sliders, navigation drawers, list items, OptionSelectors, page stack items, and text fields don't. What's the distinction?

[Tim Peeters (tpeeters)]

Thanks for re-opening and changing the title

Some list items do have haptic feedback (on release), some don't. Header buttons don't have haptic feedback, and probably haptic feedback is inconsistent among components.

We need a clear description of how the haptic feedback needs to be in general (or per-component if it cannot be done in general?), and all the components need to be checked for haptic feedback.

[Cris Dywan (kalikiana)]

The lack of feedback on certain buttons was a bug that has been fixed at this point.

[Tim Peeters (tpeeters)]

Do we need to disable the HapticsEffect in AbstractButton depending on a gsetting property? See https://bugs.launchpad.net/barajas/+bug/1358610

Or is there another way to disable all haptics in the system?