106: Sam Selikoff - Single Page Application Architecture

What It Covers

Sam Selikoff explains how to architect single-page applications by treating them as desktop apps that happen to run in browsers, focusing on client-side data management and keeping backend APIs minimal.

Key Questions Answered

• •Client-side data normalization: Build an identity map that stores normalized data locally, rendering all UI from this cache rather than individual API responses. This prevents duplicate data and keeps UI synchronized across components automatically.
• •Optimistic UI patterns: Create records in the local data store immediately without waiting for server confirmation, displaying them at 50% opacity or similar states until persisted. Handle the 0.1% failure cases separately rather than making users wait every time.
• •Offline-first architecture: Queue network requests in local storage or IndexedDB when offline, allowing users to continue working. Sync queued operations when connectivity returns, treating the client cache as source of truth that eventually syncs with server.
• •Desktop app mental model: Think of SPAs as native applications using the browser as runtime, not websites. This shifts complexity from maintaining two codebases to building one rich client with a commoditized backend API layer handling only data persistence.