Amongst the major announcements of last week’s I/O, Google’s annual developer conference, was the release of the new (& awesome) Firebase. Firebase is renowned for it’s realtime database that allows for instantly synchronizing entries between mobile clients (Android & iOS) and the web. One feature that is lesser known will be the focus of this post: the ability to host static sites and web apps.
After we’ve taken the time to explore the basic functionality of Service Worker in my most recent post, I’d like to expand on this topic by covering sw-precache (a module for generating a worker that handles precaching of your application’s resources) and how to use it with Middleman.
In today’s blog post I’d like to write about an essential component of Progressive Web Apps: the Service Worker - an event-driven background processing tool that enables fetching resources and managing your application’s cache. The result is a gain in reliable performance; connection quality and network performance loose in importance when it comes to enjoying your application.
Since my switch to Middleman I’ve been using Redcarpet as Markdown engine. The rendering engine itself ran fine but sadly doesn’t offer a way to specify custom classes for elements - a shame when you’re looking for a way to declare a certain image as img-responsive for Bootstrap et cetera.
In my most recent post I wrote about rewriting my blog from scratch and my attempts at improving it’s performance, reliability and ease of use. While exploring possible options I also investigated if it makes sense - and if it’s worth the hassle - to enable HTTPS for this site.