Re: compassCalibrated vs accuracy?

On Feb 21, 2011, at 5:52 AM, Andrei Popescu wrote:

>> Without the system UI, we're requiring:
>> 
>> - users to know how to calibrate their compass
>> - web developers to know how to explain to the every user calibration for every device type.
>> 
>> I really doubt that is possible.
>> 
> 
> Yeah, I see what you are saying...but we've seen quite a few cases
> where developers are not that happy with the browser popping up random
> UI (e.g. quota dialogs for storage APIs, etc). They'd much rather like
> to have full control over the experience the users have when using
> their application, so perhaps we should try to do away with system UIs
> whenever possible?

I agree that's a good goal. I wasn't strictly arguing against the properties in my previous email - just pointing out that I'd prefer it to be a system dialog. If a Web developer manages to confuse their user by giving a message to shake their phone in the wrong way, then that's their problem :)

> Ok. I think regardless of what we decide to do about
> "compassCalibrated", we should add the accuracy property.

That would be great. If I can expose the accuracy I'm fine with leaving compassCalibrated in.

Thanks,

Dean

Received on Tuesday, 22 February 2011 01:13:02 UTC