W28 // SINGLE PAGE APPS AND STATE
MAR 31 · Ch 12 Sec 1-3 · DUE: SPA exercises
This week's deckPPTX
// RUN OF SHOW (8:45-10:15)
8:45
Stand-up: last week's deliverable graded, questions answered
9:20
At the keyboard: guided type-along
9:45
Build time: assignment or project work
10:10
Close: commit, push, and preview next week's reading
// THE POINT THIS WEEK
What an SPA is. State as the single source of truth. Hide, show, save.
// TALKING POINTS
One page, many faces
- A single-page app swaps views instead of loading new pages
- State is the app's memory: one object holding what's true right now
- The render function repaints the page from state, every time
State drives everything
- User acts, state changes, render runs: the SPA heartbeat
- Never edit the page directly; edit state and let render do it
- This discipline is what makes big apps possible
// LINKS