W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2011

Re: [vibration] Preliminary thoughts on the vibrator spec

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Wed, 23 Nov 2011 12:34:46 +0200
Cc: Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <75C809BA-99B1-47B4-BCA4-FF42C1180ABF@nokia.com>
To: ext Deepanshu gautam <deepanshu.gautam@huawei.com>
On 23.11.2011, at 11.18, ext Deepanshu gautam wrote:

>> The proposed functionality can be used to annoy users. As a user, I
>> want to be in control of whether my device is able to vibrate (or make
>> sounds, or annoy me otherwise). 
> [DG] I'm not proposing to enable Vibration automatically (without user consent). It is just to allow Web Apps to know whether Vibrator is OFF and then notify UA. Which may then ask user to switch it on (however, that part is out-of-scope here).

Ok, but I don't see a use case for such a method either.

> This will avoid UA/OS/device to keep monitoring if some unavailable functionality is being used and then notify user.

What's the exact issue? This shouldn't be too hard to implement.

> The better way would be for *app* to say "Hey I want to use XXX would you like to switch it on" and user may decide to switch it on for that particular session, forever, forever for that particular application etc.

I think this is better handled by the *UA*. One potential implementation approach would be to do it similarly to the Geolocation API in major browsers (i.e. a non-modal infobar displayed as an extension of the chrome is asking the above question).

-Anssi
Received on Wednesday, 23 November 2011 10:35:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT