This document discusses large single page applications (SPAs) and provides recommendations for developing them. It defines SPAs as web apps that handle interactions on a single page with minimal server interaction. It recommends using libraries like Backbone or AngularJS to develop structured, modular and maintainable SPAs. It also provides dos and don'ts, emphasizing planning, testing, avoiding memory leaks, and not reinventing the wheel.

1. Large Scale SPA
A Retrospective
Reza Moaiandin
@moaiandin

2. Who am I?
Job title: Application Developer
What do I do? Front End Development + Some backend
For How long?
8 months as Front End Dev
2.5 Years as Software engineer
Strengths : JavaScript & PHP
I work for Flashtalking Leeds
Twitter: @moaiandin
@moaiandin

3. What is SPA?
“Single page applications are the modern
version of web apps where all/majority of the
interactions are handled on a single page”
They have very little server interaction (Thin Server Architecture)
@moaiandin

4. Any Examples?
What I do at Flashtalking: AdBuilder (The real deal!)
Others: Trello, Gmail, Twitter & Facebook (Almost)
@moaiandin

5. jQuery Rocks! Why should I care?
So you think you are a JavaScript Ninja?
@moaiandin

6. It’s Messy!
@moaiandin

7. Also…
Not designed for very complex applications
Lots of nested code
No Structure
Bad performance
SAD JQUERY
NINJA!
@moaiandin

8. What do we get from SPA?
Speed, Fast response time!
Modular
Maintainable
Decoupled
Extensible
Structured
@moaiandin

9. It’s nice to work on!
@moaiandin

10. How do we do it?
What do we use?
@moaiandin

11. Dos
Plan
Keep things structured
Use task runners (Grunt, Gulp)
Use libraries that work for your SPA (Backbone, AngularJS)
Don’t change path
Test
Do it right, MV*
Use routers if you need it (Keep SEO people Happy)
@moaiandin

12. Do it right, MV*
Use routes if you need it (Keeping SEO people Happy)
SERVER
MODEL
VIEW CONTROLLER
Templates View
Router
Events
Events
Events
Model Collection
Read
Update
Client Browser
@moaiandin

13. Don’ts
Don’t Try to reinvent the wheel!
Look for the tool/library you need before making it!
Don’t feel constrained to use what the library/tool gives you
Don’t write tests after development
It’s not DDT, It’s TDD!
@moaiandin

14. Don’t leave crumbs!
Look out for memory leaks, clean them up!
@moaiandin

15. Questions?
Thank you
@moaiandin