Hi everyone,
I’m working on a game project that has several dashboards displaying player progress, achievements, levels, statistics, and leaderboard information.
We’re currently using Apollo Client and have noticed that some screens trigger multiple GraphQL requests when users navigate between sections. As the amount of data grows, we’re trying to improve performance without overfetching unnecessary fields.
For teams that have built data-heavy applications with Apollo Client:
- Do you prefer a single larger query or multiple smaller queries?
- How do you organize fragments for reusable UI components?
- Have you found any effective caching strategies for frequently updated leaderboard-style data?
- Are there any GraphOS tools or Apollo Client features that help identify inefficient query patterns?
I’d be interested in hearing how others approach schema design and client-side caching for applications that need to display a lot of dynamic data efficiently.
Thanks!