HTML5 APIs You’ve Never Heard Of

A presentation at ConFoo Montreal in March 2017 in Montreal, QC, Canada by Drew McLellan

Slide 1

Slide 1

HTML5 APIs YOU’VE NEVER HEARD OF

DREW MCLELLAN CONFOO MONTREAL 2017

Slide 2

Slide 2

HTML5… APIs?

Slide 3

Slide 3

Front end Back end HTML5 APIs

Slide 4

Slide 4

The web is changing rapidly

Slide 5

Slide 5

Ch-ch-ch-changes

  • Screens are getting smaller, and bigger, and rounder, and wider, and taller, and wearable.
  • Pointing devices are becoming meatier.
  • We have access to many more hardware features.
  • Web browsers are on the move.
  • Power consumption has become a concern.

Slide 6

Slide 6

Things we can do

  • Access device sensors like the gyroscope, compass, light meter, GPS, camera, microphone.
  • Control device outputs like the speaker, vibration motor and screen.
  • Establish more app-like control of the environment our code is running in.

Slide 7

Slide 7

Page Visibility

https://www.w3.org/TR/page-visibility/

Slide 8

Slide 8

Page Visibility

Enables us to programmatically determine if a page is currently visible.

A page might be hidden if the window is minimised, if the page is in a background tab, or if the lock screen is shown.

(Plus a few transitionary states.)

Slide 9

Slide 9

Testing for visibility

The visibility of the document can be tested. You can add an event listener to be informed of when the visibility changes.

Slide 10

Slide 10

When is it useful?

Stopping ‘expensive’ operations like animation. Ensuring that the user sees important information like flash notifications or alerts. Pausing media, where appropriate.

Slide 11

Slide 11

Browser support

Slide 12

Slide 12

Use it today! There are lots of small cases where using this simple API will provide a better experience for your users.

Slide 13

Slide 13

Device Orientation https://www.w3.org/TR/orientation-event/

Slide 14

Slide 14

Device Orientation DOM events that provide information about the physical orientation and motion of a device. This is mostly useful for mobile phones and tablets. Enables us to write code that detects physical movements like rotation around a point and rate of rotation. Not to be confused with screen orientation (portrait / landscape).

Slide 15

Slide 15

Device Orientation

The API provides browser DOM events that we can attach listeners to.

The events are fired rapidly, so might need to be throttled (like we do with window scroll events).

Slide 16

Slide 16

Device Orientation

Orientation values are reported as alpha, beta and gamma properties. These are a series of rotations from a local coordinate frame. They can be used to calculate compass headings with some crazy mathematics… which is all very usefully in the spec.

Slide 17

Slide 17

Device Orientation

Orientation is expressed in a difference between the Earth frame and the device frame.

Here they are aligned.

This horrible image is from the spec, sorry.

Slide 18

Slide 18

Device Orientation

This marvellous work of art is showing the device rotated around the Z axis.

The value of Z remains the same, and X and Y change.

This results in a change to the alpha value.

Slide 19

Slide 19

Device Orientation

The beta value changes with rotation around the X axis.

Slide 20

Slide 20

Device Orientation

The gamma value changes with rotation around the Y axis.

You’re probably best to just try it. It makes more sense in action.

Slide 21

Slide 21

Device motion

The device motion events primarily give you details of acceleration.

This enables you to tell how rapidly the device is changing orientation.

Slide 22

Slide 22

Device motion

  • acceleration (m/s²)
  • accelerationIncludingGravity (m/s²)
  • rotationRate (deg/s)
  • interval (ms) (hardware capture speed)

Slide 23

Slide 23

Device motion

Acceleration, acceleration with gravity and rotation rate can all be read from the event object when listing for device motion events.

What you do with them then is anybody’s guess. Good luck.

Slide 24

Slide 24

When is it useful?

Good for creating ‘physical world’ interactions. It’s the same sensors that the Facebook mobile app uses for displaying panoramas. Could be used for game control. Makes physical gestures possible (e.g. shake to undo). Align a map to match reality…

Slide 25

Slide 25

Browser support

Slide 26

Slide 26

Browser support

Orientation is supported better than motion.

Support for orientation is pretty wide (missing in Chrome, Opera).

Missing support is often for the ever so exciting compassneedscalibration event.

Slide 27

Slide 27

Start experimenting! Browser support is not too bad. Could be interesting to use for prototypes and small projects. There might be ways motion detection could be useful for applications other than just updating a view on the screen. Lots of potential uses in mapping, gaming and health applications.

Slide 28

Slide 28

Battery Status http://www.w3.org/TR/battery-status/

Slide 29

Slide 29

Battery Status Enables us to programatically monitor the status of the device’s battery. We can see if the battery is charging or discharging, how long it will take to charge or discharge, and what the current battery level is. The interface is Promise-based.

Slide 30

Slide 30

Battery status navigator.getBattery().then( function (battery) { console.log(battery.level);

// Listen for updates battery.addEventListener( 'levelchange' , function (){ console.log( this .level); }); }); The navigator object exposes a getBattery promise. If the device has multiple batteries, the browser’s BatteryManager interface exposes a uni fi ed view. Battery level is between 0 and 1.

Slide 31

Slide 31

Battery status navigator.getBattery().then( function (battery) {

if (battery.charging) { 
 console.log( '%d mins until full' , 


Math .floor(battery.chargingTime / 60 )); 
 } else { 
 console.log( '%d mins until empty' , 


Math .floor(battery.dischargingTime / 60 )); 
 } }); By checking if the battery is charging or discharging, we can then get the time left until that action completes. If the battery is charging and we ask for the discharge time, it will be positive in fi nity which is useful to no one. The charging and discharging times are in seconds.

Slide 32

Slide 32

When is it useful? If a user’s battery is low, you might scale back on any battery-intensive actions. You might want to save the user’s progress to the server or local storage if the battery is critically low. You might perform network polls frequently when charging, but infrequently when discharging.

Slide 33

Slide 33

Browser support

Slide 34

Slide 34

Use it when available If the battery status is available, you can make use of it. If not, just carry on with whatever you were doing before. Those with supporting devices will get the bene fi t, and that’s all you can do. Not just phones - laptops too!

Slide 35

Slide 35

Vibration https://www.w3.org/TR/vibration/

Slide 36

Slide 36

Vibration Gives us access to the vibration mechanism of the device. That’s usually a phone or perhaps a tablet. Designed for simple tactile feedback only, nothing fancy.

Slide 37

Slide 37

Vibration // Vibrate for 1000 ms navigator.vibrate( 1000 ); // Vibration to a pattern navigator.vibrate([ 150 , 50 , 150 ]); // Cancel any vibrations navigator.vibrate( 0 ); Vibration time is set in milliseconds. When an array is given, the even items are vibrations, the odd items are pauses. This enables more complex patterns. Any ongoing vibration can be cancelled.

Slide 38

Slide 38

When is it useful? Providing tactile feedback for important actions. Could be used as a rumble in games. Create a cool Morse code device?

Slide 39

Slide 39

Browser support

Slide 40

Slide 40

Use it! Works in most mobile browsers other than iOS Safari. Should be safe to use as an extra where it is supported. Don’t design interactions that rely on it, and maybe check battery status too!

Slide 41

Slide 41

Web Noti fi cations http://www.w3.org/TR/noti fi cations/

Slide 42

Slide 42

Web Noti fi cations Enable us to issue an alert to the user outside the context of the web page. This is normally through the operating system’s standard alerts mechanism. Users must grant permission before noti fi cations can be shown.

Slide 43

Slide 43

Web Noti fi cations if ( 'Notification'

in

window ) {

// Notifications are supported! } Notification .requestPermission( function (status) {

if (status

'granted' ) {

// We have permission to notify! }; }); We can test for the Noti fi cation property of the window object to see if we have support. Before sending a noti fi cation, we need to request permission. This call returns either ‘granted’, ‘denied’ or ‘default’. We can only send a noti fi cation when the result is ‘granted’.

Slide 44

Slide 44

Web Noti fi cations var notification

new Notification( 


'Your life is in danger' , 


{ body :

'You forgot to take your pills' , icon :

'skull-and-crossbones.png'

} 

); The Noti fi cation constructor takes a title, and then an object containing options. Basic options are ‘body’ for the message and ‘icon’ for an icon to show with the noti fi cation.

Slide 45

Slide 45

Web Noti fi cations var notification

new Notification(

'Your life is in danger' , { body :

'You forgot to take your pills' , icon :

'skull-and-crossbones.png' , tag :

'pills-warning' , lang :

'en-US' , dir :

'ltr'

} 

); The ‘tag’ option acts like an ID for the noti fi cation. If there are multiple instances of your code running (e.g. two browser windows) the tag prevents the noti fi cation being duplicated. It can also be used to address the noti fi cation to cancel it.

Slide 46

Slide 46

Web Noti fi cations notification.onclick

function () { console.log( 'Notification clicked on' ); } onclick onclose onerror onshow Noti fi cations have corresponding events to enable you to track their state. (In theory. I actually couldn’t get these to work.)

Slide 47

Slide 47

What are they good for? Notifying the user of background task completion, e.g. encoding has fi nished, upload has completed. Notifying of incoming activity, e.g. a message has been received, a user has logged in.

Slide 48

Slide 48

Browser support

Slide 49

Slide 49

Use them! Pretty great support on desktop. Judge carefully when to ask permission to display notifications. Do it before you need to send, but not before the user trusts you or they’ll decline.

Slide 50

Slide 50

Web MIDI https://www.w3.org/TR/webmidi/

Slide 51

Slide 51

MIDI?!

Slide 52

Slide 52

Musical Instrument Digital Interface MIDI is a very well established protocol for sending event messages about musical notes, control signals and clock signals. It’s used by musical keyboards, synths, drum machines, digital control surfaces, theatre lighting and sound systems, and most importantly…

Slide 53

Slide 53

Keytars!

Slide 54

Slide 54

Web MIDI MIDI sends note-on and note-o ff events (with pitch and velocity), and change events for any number of other controls. It’s basically a well de fi ned protocol for event based input and output for physical buttons and switches. Which makes it quite exciting.

Slide 55

Slide 55

Web MIDI if (navigator.requestMIDIAccess) {

// We have MIDI support! } if (navigator.requestMIDIAccess) { navigator.requestMIDIAccess() .then(success, failure); } We fi rst need to request access to MIDI devices. This returns a promise, with a success and failure callback. Code sample references work by Stuart Memo on sitepoint.com

Slide 56

Slide 56

Web MIDI function failure() {

// MIDI access denied :( } function succes s(midi) {

var inputs

midi.inputs.values();

for ( var input

inputs.next(); input &&

! input.done; input

inputs.next()) {

input.value.onmidimessage 

= messageReceived ; } } If we have access to MIDI, our success callback gets a MIDIAccess object. From this we can get all the di ff erent MIDI inputs we have access to, using an interator. This code loops through the inputs adding an event listener for the onmidimessage event.

Slide 57

Slide 57

Web MIDI function messageReceived (message) { console.log(message.data); } [ 144 , 61 , 95 ] [ 128 , 61 , 0 ]

[ eventCode , note , velocity ] Now we can receive MIDI messages! They look weird. The format is event code, note number, velocity. 144 is note on. 128 is note o ff .

Slide 58

Slide 58

Demo!

Slide 59

Slide 59

When is it useful? Simple integration between physical devices and the browser. There are lots of MIDI devices and most are very robust. Designed to be hit with sticks etc. Perfect for children’s games, controls for those with disabilities, kiosk applications, keytars.

Slide 60

Slide 60

When is it useful? You can also play notes out, enabling you to play instruments, control theatre lighting, sound e ff ects, video playback. It will not give you any musical talent. Sorry.

Slide 61

Slide 61

Browser support

Slide 62

Slide 62

Play with it Could be fun for hack projects, and controlled environments. Might not quite be ready for the open web until all computers ship with keytars. Keytars!

Slide 63

Slide 63

Phew.

Slide 64

Slide 64

HTML5 APIs Page Visibility Device Orientation Battery Status Vibration Web Noti fi cations Web MIDI Ambient Light Geolocation Web Audio Web Share Payment Request Screen Orientation

Slide 65

Slide 65

HTML5 APIs Clipboard Speech synthesis Speech detection Media capture streams Proximity Network information File & File System Drag and drop Fullscreen Web workers

Slide 66

Slide 66

Thanks!