- From: Josh Soref <jsoref@rim.com>
- Date: Wed, 23 Nov 2011 17:21:00 +0000
- To: Deepanshu gautam <deepanshu.gautam@huawei.com>, Anssi Kostiainen <anssi.kostiainen@nokia.com>
- CC: Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Anssi wrote: > Ok, but I don't see a use case for such a method either. DG wrote: > I disagree :-) This isn't how you get things added in our Work Mode. DG wrote: > It is not about hard of easy, it is about making this API more complete > for our developers. Our design premise is that we make the simplest API possible to enable a basic UC. Adding extra knobs is not something we do. Especially things which the UA needs to be able to manage on its own. And if there's a chance that the UA can't answer the question, then we really don't want to do it. It's possible a UA doesn't/can't know if vibration is enabled/disabled, and we definitely don't want to create events to tell the app "vibration is now available", "vibration is no longer available". DG wrote: > I think I have said what I could already to prove my point. It is not > like I want this to be handled by App solely (it is not possible actually). I > just want to make our developer (those who really want to) write good quality > application enhancing user experience and try to do it as much as they can > from their part and not relying on UA. I can abandon an app and choose a > similar from another developer but it is difficult for me to change my UA. Unfortunately this isn't always the case. Users are often stuck with bad apps. Leaving some control at the UA to enable users to live with bad apps is important. --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 23 November 2011 17:22:35 UTC