Slowdown and New Projects

I started a contract in early June that has swallowed all my time and as a result there have been fewer blogs and, I hate to admit it, with a lower quality than I would like. I also have a few projects that I’ve been working on for a while and that I want to finally finish and put to rest. These projects (and some of the questions they seek to answer) are: Long form publishing using Service Workers: An exploration of how far we can push the web as a publishing medium. What can we do beyond offline? Is

EME, DRM and The Web Platform

The EME controversy rears its ugly head again but this time it seems like it’s going to end poorly for users and rather well for content creators. EME as currently implemented would enable closed source DRM on web browsers for movies and tv series through vendors like Hulu and Netflix among others. EME is based HTML5 Media Source Extensions, which enables adaptive bitrate streaming in HTML5 using e.g. MPEG-DASH with MPEG-CENC protected content. These forms of protected contents are protected by legislation pieces like Section 1201 of the The Digital Millenium Copyright Act in the US; European laws that implement

Designing a service worker

Since I decided to do an app shell architecture for the project we’ll have to split the way we cache content with service worker. We’ll use both sw-precache to cache the app shell and sw-toolbox to cache the other pages of the application and any associated resources. Yes, we could build the service worker manually but updating becomes more and more complex. You have to remember to update the worker whenever you make a change and that makes it error prone. I don’t particularly like using third party libraries to build my code but in this case the advantages far

Reading for everyone

Third in a series. Other two parts are What kind of web do we want? and Who are the next billion users and how do we accommodate them How we build content that will be read wherever and whenever we are regardless of the device we use to access it? Reading for everyone I’ve also found myself in discussions on Medium about Portable Web Publications and when I asked what happens to people using existing devices (I used Kobo and iBooks as examples) I was told that PWP are web applications not ebooks. So what do you do in devices

What kind of web do we want?

The web, technology wise, is in a great place. We’ve grown closer to parity with native apps, that’s the gist of progressive web applications, we can have pretty close to the same experience form web apps as we can from native. Javasacript has improved both in terms of speed and interoperability. New HTML5 APIs have contributed to Javascript resurgence and popularity. It’s also new features in ES6 (ratified in 2015) like classes, standardized modules and other APIs make it fun and useful to code in vanilla Javascript. CSS has moved forward y leaps and bounds. We can do a lot