2016 began with a spanking new dashboard for Instamojo merchants and buyers.\u00a0Post that big release, every now and then we take time out from our tasks (read – new features, bug fixes and support) to\u00a0think about ways in which we can be progressive and serve users who are using a variety of devices and browsers out there.<\/p>\n
Making a site work offline is not a product requirement – unless that\u2019s what you\u2019re building. Besides, it’s probably not for a\u00a0startup trying to ship things fast and get things done.<\/p>\n
At Instamojo, us frontend engineers drove the entire initiative with (very minimal involvement of)** the product managers and designers.<\/strong><\/p>\n Thousands of merchants and buyers log onto their Instamojo dashboard on a daily basis.<\/p>\n About 25% of such users come via mobile devices, usually on a flaky internet connection.<\/strong><\/p>\n With the goal of reducing\u00a0both,\u00a0perceived and actual load times for such users, we started serving all network requests via Service Workers.<\/p>\n All static assets are cached the first time they are fetched from network and all such subsequent requests are served from this Service Worker cache.<\/p>\n All dynamic calls are requested first via the network with a timeout which then falls back to a response in the Service Worker cache. See it in action below:<\/p>\nElements of Instamojo offline<\/h2>\n
The Service Worker bit<\/h2>\n