In the last post about powerful new APIs we talked about Service Worker, notifications, push and more. This week we got some other news, videos, slides and a new slack channel for web developers that you should take part in.
New Stuff Around The Web
- Google Tone is an experimental Chrome extension for sharing the URL of the current tab with other computers by using audio!
Yes, it does not use Bluetooth, NFC or WiFi: it only sends audio waves. “Google Tone turns on your computer’s microphone (while the extension is on) and uses your computer’s speakers to exchange URLs with nearby computers connected to the Internet.”
- Can web apps be as smooth and slick as native? YES!
Paul Lewis made a web app to show how. The app uses all the latest goodies, including Service Workers, ES6 Classes and Fat Arrow functions, and Promises.
Check out his blog post here for all the details!
- The best (new) show in town about best practice tools.
- Another new location we maintaining to hold all the news around web development: https://developers.google.com/web/updates/ and if you like medium we got a new channel there as well.
- Polymer 0.9 library is released!
The 0.9 release is very similar to 0.8, with many of the “experimental” 0.8 features now officially supported.
Full release notes for 0.9, including the breaking changes from 0.8, are available on the Polymer site.
- Two new videos from talks that Paul Lewis and Jake Archibald gave last week:
Chrome 42 (stable)
- The Push API and Notification API are available to developers. The Push API in Chrome relies on a few different pieces of technology, including Web App Manifests and Service Workers. If you wish to talk with us about Push – please feel free.
- A little-known feature in Android lets you launch apps directly from a web page via an Android Intent.
Learn more: developer.chrome.com/multidevice/android/intents
Chrome 43 (Beta)
- A summary video on new features: Cut and Copy, changes to DOM attributes & WebMIDI.
- The Fetch API now allows developers to directly operate on and incrementally release the bytes of streamed network responses, in contrast to the equivalent XMLHttpRequest functionality that requires developers keep the entire in-progress stream response in memory.
- The Cache Storage API, previously only available in service workers, now provides developers full imperative control over their caching in the page context.
- Chrome OS now fires devicemotion events on pages at a regular interval, allowing developers to track the device’s acceleration in the same way they do on Chrome for Android, Windows, Mac, and Linux.