[lucfranken]

While interesting be aware of those quotes from the article:

About offline:

> Local storage action creators & epics (~1000 LOC). This is a bit unfair to count in the total because offline support for our project is postponed, but it’s achievable if we want to add it back in by customizing the Apollo fetchPolicy & exposing the reducer to redux-persist.

About mutations (insert/update/delete statements):

> While our server is currently “read only,” we may need to introduce mutations in the future to save a user’s favorite team.

When considering GraphQL test those as well because the "loading data" part is very cool and easy to grasp. It gives instant results, really cool.

Updating data is not as easy as that and not as mature yet. There is an ongoing process of finding how to update the local data store.

See for example comments in the documentation: http://dev.apollodata.com/react/cache-updates.html#updateQue...

So while it's a great tool understand your app's processes before diving in completely.