Om Next
summary
Om Next proves components declare static component queries (composable pull-style fragments) so the client gets back exactly the shape requested via GraphQL/Falcor-style demands; a working prototype composes queries across components, removes cursors by building runtime indexes, and keeps a single store with asynchronous render ticks and easy rollback. Demo shows a static get-query call returning only requested fields, live-updates via Figwheel/Amble to iOS simulators, and feasible backends using Datomic or Falcor routers; the prototype runs and composes queries end-to-end.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:58React Framework
- 3:14Om Principles
- 5:23Cursors
- 7:03Seamless Sync
- 7:56The Problem
- 11:10Demand Driven Design
- 13:28Relay
- 14:50Falkor
- 17:11Atomic
- 18:23Simple Data
- 22:07Give each component
- 23:05No cursors
- 24:00No render loop
- 25:46Om Next demo
- 30:48Query updating
- 31:22Closure Script
- 32:46The Big Plan
- 33:11Google Summer of Code
- 35:16Shoutout to Maria
- 35:30Amli
- 39:57Shoutouts
- 40:07Close Your Script
- 40:33Awesome Demos
- 45:13More Shoutouts
related talks
38mClients in control: building demand-driven systems with Om Next
28mGraphQL without GraphQL - Backend Agnostic GraphQL inspired Queries For Colocating Data Requests With Components
21mHow Next.js is delivering React’s vision for the future
20mColocating & Composing Data Dependencies with Fragments
41mReact Query: The Next Big Library?
25mReact Query Under the Hood
27mThe Functional Final Frontier
37mAll you need is l̶o̶v̶e Apollo Client