Is there a general guideline for application developers about when to
disable haptic responses?  I know there are ways to enable/disable
long-press haptics, but if an application was created to use haptic
feedback for other events are there guidelines that application
developers should follow?

For example, if the user was to go into Settings->Sound & display ->
Haptic and set that to OFF, should all applications refer to this
setting as a rule of thumb?  From and end user point of view, I would
like to have global control of haptic feedback especially if I find it
to be annoying.  I have seen several postings in the android forums
looking for a "global override" to haptic responses.  Ultimately, I
think it is a question of should each application provide a menu to
enable/disable haptic support, or should this be more of a global
Setting for the device.  I personally feel applications should refer
to the global setting, but would like to get feedback from other
developers about this.

Reference postings I was referring to:
http://www.droidforums.net/forum/droid-general-discussions/6812-haptic-feedback-dial-pad.html
http://androidforums.com/samsung-moment/13633-how-do-you-disable-vibrating-feature-soft-keyboard.html

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to