We recently completed a sprint on a big feature set for one of our Angular.js projects: offline mode. The goal was to enable the user to perform as many actions offline as possible, all while maintaining a smooth, reliable experience with no data loss.
This is not a blog post about the general capabilities of offline mode in HTML5, nor a how-to guide for setting up offline mode in your app. (Here is a great resource for that, if that’s what you’re looking for.) This blog post will address the quirks and edge cases that came up in real life development. Hopefully they’ll save you some time with your projects!
Application Cache is one of the hottest new features available in modern browsers. Here's how we leverage it at Quick Left.
Did you know that typeof [ ] evaluates to an object? Funky stuff.
Get up to speed on Chrome's complex caching system.
The evolution of JS Lint begins.
Google web fonts
Google's new hosted web font service.
Deciding which metrics are valuable and which are garbage.
Easily run a custom script on any page, every time it loads.
The HTML5 spec pared down for developers, not browser builders.
CMS on top of Sinatra. Heroku ready. Developer friendly.
Quick Left-overs is a weekly series of things that end up in our "FancyBookLearning" Campfire room that we thought were interesting.
Live in-browser CSS editing HTML5 hack using contenteditable.
Recently, there has been lots of hype surrounding the topic of Flash vs. HTML5. Apple released the iPad this Spring--Adobe Flash player incompatible--splitting the internet into two battling sides: Flash and HTML5. Here at Quickleft, we decided to put some HTML5 performances to the test.