GET what you need and drop the REST
summary
A small table‑football scoring PWA uses GraphQL as a single API endpoint so the client posts queries that request exactly the fields needed and the server resolves fields on demand; mutations handle create/update/delete, tooling uses schema introspection for validation and docs, binaries are served by generate URL to classic REST for binaries while dynamic images use hashed URLs, offline works by precache GraphQL data and disabling mutations, and overall the app runs offline after install with live refresh from the network.
AI-written summary · about
related talks
37mGraphQL — A New Look at the API
46mGraphQL 101 - Stop RESTing, Start Querying
36mGraphQL Will Do To REST What JSON Did To XML
41mDemand Driven Applications with GraphQL by Vinci Rufus
33mGraphQL Will Do To REST What JSON Did To XML
17mThe Power of GraphQL
59mGoodbye REST; Hello GraphQL
41mDoes Your API Need a REST? Check Out GraphQL.