Our upcoming Backbone.js frontend is quite complex. When we considered our inexperience with Backbone, it made sense to start off with a simpler project to focus on getting the models and collections correct before worrying about views. We built a simple Chrome Extension to test the waters and learn more about Backbone. Our design philosophy emphasizes an accessible backend API that can be used for different frontend applications. This allows us to create separate frontends for desktop, Android, iOS, or even a Chrome Extension from the same data source. The most difficult concept in Backbone is views, which require convention over code, but we created a simple Viewport view to control content loading and unloading. We also wrote our Backbone code using Coffeescript, RequireJS, and the Use Requirejs Plugin. Developing the Chrome Extension was relatively straightforward, with minimal surprises, especially since it only required generating a popup and utilizing Chrome's browser_action definition in the manifest.json file. Storing locally is essential for models and collections, as they are re-loaded each time the popup is opened, so we used LocalStorage API to cache data or persisted it into the background page. Once completed, our project was packaged up using the built-in extension packager, which demonstrates the power of a separated backend API and Backbone's applicability to different frontend views.