Comment 5 for bug 1474226

Fair enough, Won’t Fix was hasty. Marking as Incomplete, because there isn’t enough information to determine that there’s a problem. Even if you took a long time to find the settings (which isn’t clear from the bug description), moving or renaming them might not improve things for people on average. Moving them might make people slower or less successful on average, and renaming “Sound” might make people slower on average in changing settings in general.

Part of the reason I’m skeptical that it’s a problem is that vibration settings are also found under “Sound” on Android and iOS.
<https://support.google.com/nexus/answer/2819577>
<http://www.imore.com/how-set-custom-alert-vibrations-or-disable-them-your-iphone-and-ipad>

In general we have the time and budget to test only high-risk designs, so for most things we rely on experience and judgement even if there’s an anecdotal bug report about them. But as design questions go, this would be quite easy to test if you wanted, because you could use paper prototyping. <http://alistapart.com/article/paperprototyping> Print screenshots of the current interface, and of the interface doctored in some way that you think might work better. Test ten participants with each (not the same ten with both!), asking them something like “Imagine that you got this new phone, and you were getting annoyed that it vibrates while you’re playing games. Where would you go here to stop that from happening?” Start your stopwatch when you finish asking the question.