As consumers of information we’ve all become more demanding. We want the content faster and we want to be engaged with the content we access online. PSPs should be no different in their performance to...
We want our content to look awesome regardless of the device. How do we accomplish this? A good starting point is Ethan Marcotte’s Responsive Web Design (or whatever Responsive Web Design book is your...
I still remember the first time I made an annotation from a Kindle book available in their public site (kindle.amazon.com). I saw the possibilities as limitless until I realized that there were...
The service worker script we discussed in the prior section is the core of a PSP but there’s way more we can do to make our reading experiences behave more like native applications. Some of these...
How does this all work? # At the core of our progressive subcompact publications is a service worker. This woker is a type of shared worker and it also works as a network proxy for your requests, you...
For the past few months I’ve been working at Google building a set of instructor-led courses on how to build progressive web applications. This has made me think of how to push some of these concepts...
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...
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...
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...
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...