Architecting Data-Driven Apps for UX Success
summary
Shows a small app called Waterfall Chaser app that first issues N+1 queries then is refactored to collect data in one round trip using fragments to compose queries, demonstrating a measurable drop in network round trips. Implements React hooks and Apollo Client hooks (useQuery, useMutation), adds optimistic UI via optimisticResponse so likes increment instantly while the network is pending, and documents that optimistic updates work but require explicit error handling, Storybook/Chromatic for component QA, and Apollo Studio for schema and rollout control.
AI-written summary · about
chapters (7)
- 0:00Introduction and overview
- 6:20Data-driven app challenges
- 13:52Optimizing data loading with fragments
- 20:10Reactivity and user feedback
- 32:20Modern tooling and ecosystems
- 39:09GraphQL and Apollo Studio benefits
- 44:12Q&A and migration tips
related talks
23mOptimistic UI updates with Apollo Client and React
52mState management in a GraphQL era
26mData Fetching Unleashed: Next.js, React Query and their BFF
24mRethinking frontend architectures with data layers
36mThe State Management Rollercoaster
38mThe Front End Architecture Revolution
21mHow not to end up your app to a hot mess of spaghetti Carbonara
20mColocating & Composing Data Dependencies with Fragments