W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2009

Re: ISSUE-16: Gathering requirements [User Interaction API]

From: Robin Berjon <robin@robineko.com>
Date: Tue, 20 Oct 2009 18:58:50 +0200
Cc: "Anssi Kostiainen" <anssi.kostiainen@nokia.com>, "ext Brian LeRoux" <brian@westcoastlogic.com>, "Device APIs and Policy Working Group WG" <public-device-apis@w3.org>
Message-Id: <3E75AFCE-067A-44DC-806E-A0C748AF50C9@robineko.com>
To: David Rogers <david.rogers@omtp.org>
On Oct 20, 2009, at 16:27 , David Rogers wrote:
> "
> Then there is the other side which is that the developer may wish to
> use the vibration mechanism (say, for instance, to match collisions in
> a game). This is a vibrate() API, and if the device can't vibrate then
> I expect that nothing happens (or some other error handling  
> mechanism).
> "
> [DAVID] - I would expect there to be feedback via an error to the  
> effect
> that 'the feature is not supported on the device'

Ideally the developer ought to be able to detect that vibrating is not  
available, but IMHO it shouldn't interrupt program flow. That way  
sloppy code won't cause the bad UX of the app stopping without the  
user being able to do anything about it.

Robin Berjon
   robineko  hired gun, higher standards
Received on Tuesday, 20 October 2009 16:59:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:12 UTC