Sam is a Developer Advocate
Auditing your site or app will help you build a resilient, performant experience — and highlight quick wins that can be implemented with minimal sign-off. An audit also gives you a baseline for data-driven development. Did a change make things better? How does your site compare with competitors? You get metrics to prioritize effort, and concrete evidence to brag about once you've made improvements.
There are several core objectives for building a performant, resilient site with low data cost. For each objective, you need an audit.
You won't be able to build a PWA without HTTPS. Serving your site over HTTPS is fundamental for security, and many APIs won't work without it. If you need to justify implementation costs, find out why HTTPS matters.
Having completed a site audit, you should have accurate review data in a form that makes it easy for developers and other stakeholders to prioritize and justify changes.
Before gathering performance metrics for a site audit, there are several checks you can do to identify easy fixes and areas for focus. Some of these checks are relatively subjective, but can identify problems that affect perceived performance.
Once you've audited a site, make sure to package the results in a digestible form. Be sensitive to the people on the receiving end of your audit, structure your report carefully and present your data in terms of opportunities and solutions.
Image Capture is an API to control camera settings and take photos.
captureStream() method makes it possible to capture a MediaStream from a canvas, video or audio element.
Muted autoplay for video is supported on Android from Chrome 53. Previously, a video element required a user gesture to initiate playback.
From version 52, Chrome uses ECDSA by default — a much more efficient and secure algorithm for WebRTC certificate key generation. In addition, RTCCertificates can now be stored with IndexedDB.
From version 52, Android Chrome uses the same media stack as desktop Chrome, rather than relying on the underlying platform implementation. This enables service worker media caching, variable playback rates, blob URLs on Android, MediaStream passing between APIs, and easier cross-platform debugging.
Consider content as well as layout and graphic design when building for a range of users and devices.
It's important to understand what using your app or site feels like when connectivity is poor or unreliable, and build accordingly. A range of tools can help you.
The MediaRecorder API enables you to record audio and video from a web app. It's available now in Firefox and in Chrome for Android and desktop.
From Chrome 48 on desktop and Android, VP9 will be an optional video codec for video calls using WebRTC.
Chrome on Android now allows mobile sites to present to Google Cast devices using the Presentation API and the Cast Web SDK.
Chrome 47 has several significant WebRTC enhancements and updates including audio and video recording, proxy handling and mandatory secure origins for getUserMedia().
The MediaDevices interface gives access to input and output devices available to the browser including cameras, microphones and speakers.
EME Logger is a Chrome extension that logs Encrypted Media Extensions (EME) events and calls to the DevTools console.
The MediaStream API represents synchronized streams of audio or video. MediaStream.ended, MediaStream.label and MediaStream.stop() are being deprecated. Use MediaStream.active, MediaStreamTrack.label and MediaStreamTrack.stop() instead.
When audio or video is playing on a web page, a notification showing the page title and a play/pause button is displayed in the notification tray and on the lock screen. The notification can be used to pause/resume play or return to the page playing the media.
Hardware video support brings efficient decoding to plugins as well as HTML5 video. Flash users should switch from the old style Video to the StageVideo object.
Learn about the simplest ways to add video to your site and ensure users get the best possible experience on any device.
Enabling HTTPS on your servers is critical to securing your webpages.
The capabilities of the Open Web Platform is accelerating at a pace that has never been seen before. At the Chrome Dev Summit we talked about how we are working on improving Blink, Security and Media for the platform
WebM just added alpha transparency, and support for it has landed in Chrome 31.