>This was a terrible idea from the start. In the best case scenario, what is supposed to happen? I see two scenarios here: 1. The usual cock-up of the API guy

>This was a terrible idea from the start. In the best case scenario, what is supposed to happen? I see two scenarios here: 1. The usual cock-up of the API guys not being the privacy/security guys and managers being unable to find common ground between the two. 2. The pressure to make HTML5 be an "app killer" and making sure devs have everything they need to write HTML5 web apps that can compete with native apps. Security/privacy becomes a browser problem, and if the browser guys screw up (see 1.) then too bad. Seems to me, a simple middle ground of reporting a less granular battery value would have made sense. Very Low, Low, Medium, High, Very High would probably take care of it. You can probably just shoe-horn this in right now by just assigning a number to each condition and never telling websites the real number (or randomizing it a bit).