With the increasing adoption of progressive web apps, the web platform is becoming more attractive every day. However, in order to complete the circle and provide all the tools and APIs developers need, we must expose the hardware sensors. Historically, the web platform has lagged in exposing low-level features, due to privacy and security concerns and the complexity of the task. This challenge is finally solved with the W3C Generic Sensor API, which creates a modern, forward-looking base API to expose hardware sensors (e.g., ambient light sensors and motion sensors).
Thanks to this API, it’s now easier to create web-based games that leverage sensors or just improve the usability of any website. You can also leverage this API on Node.js- or JavaScript-based environments for targeting the IoT. Alexis Menard offers an overview of the new W3C Generic Sensor API, showing examples of how to use the API and diving into the current status of the spec and the implementation. Join in to learn how you can implement it today and catch a glimpse of future plans.
This session is sponsored by Intel.
Alexis Menard is a software engineer at Intel’s Open Source Technology Center in Portland, Oregon. His main focus is on the ever-evolving WebPlatform, which includes work on W3C standards as well as Blink/Chromium. In the latter projects, he serves as both developer and code reviewer. Alexis also worked on Crosswalk, an HTML5 runtime/webview for Android, where he did a bit of everything. Prior to Intel, Alexis worked on QtWebKit and WebKit at the Brazilian Nokia research center (INdT) and on the Qt framework as a part of Nokia (former Trolltech). He is also a former KDE contributor, contributing mostly to Plasma, the desktop shell of KDE.
For exhibition and sponsorship opportunities, email fluent@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of Fluent contacts
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • confreg@oreilly.com