RedDotRubyConf2014

To A Single Page Web App and Back Again. The story of Shopify's experience building a Js MVC framework and a single page web app. Lessons we learned and why we moved to a hybrid approach.

1. To a Single Page Web App… and Back Again Nick Simmons RedDotRubyConf Singapore 2014
2. “WHO IS THIS GUY?”
3. CANADIAN
4. I LIVED HERE
5. WHAT I DO NOW
7. SHOPIFY ADMIN EVOLUTION Admin Classic: + ERB + Admin 2: Admin Next: ...
9. SHOPIFY - MAY 2013 + =
10. BUT... “Batman is hard!” - said everyone.
11. LEARNING BATMAN Superhero Newb Time Read Admin code Read Batman docs Back to Admin code Ask for help Read Batman code
12. HACK DAYS - JUNE 2013 “Let’s use Batman for our project!” “Where do I start?” “HELP!” “F**k this, I’m using Rails”
13. LESSON #1 Solid documentation and excellent examples are vital to framework adoption.
14. NEW FEATURES - JUL TO NOV 2013 “Where should I put this code?” “I’m a frontend dev, client has all the state that I need.” “Let’s do it client side!”
15. THE RISE OF POS JSON API BUSINESS LOGIC BUSINESS LOGIC
16. LESSON #2 Minimize business logic in the client.
17. BATMAN DEEP DIVE - DEC 2013 “The Admin is looking a little janky.”
19. BINDINGS IN ACTION
20. ORDER PAGE BINDINGS
21. THE COST OF BATMAN
22. LESSON #3 JS MVC is a great technology, but not for our app.
23. ADMIN REBOOT
24. ADMIN-NEXT GOALS • Easy to use. • Keep the good bits. • Fast… (er than Batman)
25. WHAT IS ADMIN-NEXT? Turbolinks (modified) Bindings.coffee + +
26. LESSON #4 A simple approach scales better than a complex one.
27. How are we doing?