Using the Accelerometer in your Web app

No, unfortunately, this isn't a post about how to use the accelerometer in your web app. But if you thought it was, read on.

I'll be honest. As an Intel employee, I care about exposing our hardware so that applications can take advantage of it. But why should you care about the platform as you write your web app? Isn't that the whole point of the the Internet, browsers-as-a-platform, and cloud computing: so that you can truly write once on the backend and your app runs everywhere without a hitch? If you start caring about what your customer's platform or environment are like...yikes! That's a lot of extra work!

You may not care about how many cache lines there are in the CPU as you pick your main page color scheme and create your database tables. But what about the geolocation of your customer? or the ambient light or even ambient temperature where they are using your app? What kind of customer experience could you create if you knew how much battery power was left before you streamed them a movie? Or automatically saved their blog entry to their local storage when you detected that the connection to the server went bad?

Clearly, there is balancing act to be struck between the low maintenance cost and fast time to market of a purely client-agnostic web app, and the application that just knows about your customer (with their permission, of course) and keeps them coming back for more.

Where are you on the spectrum? If all of the plugins, intallations, standards and security issues could be resolved, what would you like to see in the browser? The W3C is starting to tackle these issues in a new Working Group, meaning that in the future, you might be able to access the camera or a microphone from your web app.

If you have ever thought "Just think what I could do, if only my web app could access the _______," what is it that you'd like to see?

Para obtener información más completa sobre las optimizaciones del compilador, consulte nuestro Aviso de optimización.