What new APIs should W3C work in to allow powerful mobile web applications? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. 开发者_StackOverflow Closed 9 years ago.

As an amateur mobile developer, I feel dismay every time I have to fix, update or add new features to an application of mine.

I'm eagerly awaiting the moment you can just develop a web application for any kind of device.

HTML5 and new APIs like Geolocation API or Contacts API are a step forward, but what other APIs could be useful to move current mobile developers to the web? For example, some kind of Sensor API to access mobile accelerometers or magnetometers.

I am aware that future Flash and AIR mobile releases are coming, but I'd rather prefer web standards.

---

There’s an idea to add a general devices API to HTML5.

http://www.w3.org/TR/dap-api-reqs/

To be honest, I don’t think you can do this sort of thing generically (or at least it’s an impractical challenge). I think it’s down to the folks who make mobile operating systems — i.e. Apple, Google, and the rest — decide whether and how to provide JavaScript access to hardware.

It’s potentially a massive security risk. Go to a hijacked website, and suddenly Russian criminals are copying every photo you take? There’s a “powerful mobile web application” for you.