Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Building our first single-page app

Building our first single-page app

Presented at the March 2013 @DjangoToronto, A somewhat high level overview of how we've built our single page app, challenges, and moving forward.

Avatar for Bartek Ciszkowski

Bartek Ciszkowski

March 22, 2013
Tweet

More Decks by Bartek Ciszkowski

Other Decks in Programming

Transcript

  1. • “Time to first tweet”, rendering essentials as soon as

    possible. • Mobile web is dead. Long live the web • Limited/unavailable data connection. Global issues. Thursday, March 21, 13
  2. • Potential for duplication on server/client • Javascript community, the

    wild west • Bootstrapping vs. data on demand Challenges Thursday, March 21, 13
  3. Why Backbone? • We wanted to learn how to write

    proper Javascript • Our app was small enough that we could build the scaffolding ourselves (with some help from Marionette) Thursday, March 21, 13
  4. Initializing the app Global app object starts everything. Handle routing,

    caching Initializes with modules, which are agnostic of the app Thursday, March 21, 13
  5. Ready to deploy • r.js optimizer takes all your hard

    work and merges it into a single file. • Almond.js removes dependency on requirejs include. Thursday, March 21, 13
  6. Someones already done what you’re trying to (but it may

    be deprecated already for something else. Follow the yellow brick road!) Thursday, March 21, 13
  7. Self contained modules "the UNIX way of tiny self-contained modules

    that each do just one thing" -- http://substack.net/ Thursday, March 21, 13
  8. Resources • AirBnB Tech Talk on Single-page apps by Spike

    Brehm • RequireJS Multi-page shimmed site • Making life easier with Grunt • Building the next Soundcloud • django-requirejs-boilerplate by Thursday, March 21, 13