Getting Began with GraphQL and React Native

In 2012, Fb engineer Nick Schrock began work on a small prototype to facilitate transferring away from an previous, unsupported companion API that powered the present Fb Information Feed. On the time, this was known as “SuperGraph”. Quick ahead to as we speak and SuperGraph has helped form the open-source question language GraphQL, which has been a lot of the buzzword in current instances.

Fb describes GraphQL as a “question language for APIs and a runtime for fulfilling these queries together with your current knowledge”. Put merely, GraphQL is a substitute for REST that has been steadily gaining recognition since its launch. Whereas with REST a developer would often collate knowledge from a collection of endpoint requests, GraphQL permits the developer to ship a single question to the server that describes the precise knowledge requirement.

Need to study React Native from the bottom up? This text is an extract from our Premium library. Get a whole assortment of React Native books protecting fundamentals, tasks, suggestions and instruments & extra with SitePoint Premium. Be part of now for simply $9/month.


For this tutorial, you’ll want a primary data of React Native and a few familiarity with the Expo surroundings. You’ll additionally want the Expo consumer put in in your cell system or a appropriate simulator put in in your pc. Directions on how to do that may be discovered right here.

Undertaking Overview

On this tutorial, we’re going to demostrate the facility of GraphQL in a React Native setting by making a easy espresso bean comparability app. In an effort to give attention to all the nice issues GraphQL has to supply, I’ve put collectively the bottom template for the applying utilizing Expo.

To get began, you may clone this repo and navigate to the “getting-started” department, which incorporates all of our primary views to begin including our GraphQL knowledge to, in addition to all of our preliminary dependencies, which at this stage are:

“expo”: “^”,
“react”: “”,
“react-native”: “”,
“react-navigation”: “^three.6.1”

To clone this department, you’ll have to open up terminal and run this command:

git clone

To then navigate to the getting-started department, you progress into the newly cloned repo with cd graphql-coffee-comparison and run git checkout getting-started.

The subsequent stage is to put in our dependencies. To do that, ensure you’re on Node v11.10.1 and run npm set up within the root listing of the mission. It will add all the dependencies listed above to your node_modules folder.

To start out including GraphQL to our React Native app, we’re going to want to put in just a few extra dependencies that assist us carry out just a few easy GraphQL capabilities. As is widespread with trendy JavaScript improvement, you don’t want all of those dependencies to finish the info request, however they actually assist in giving the developer a greater probability of structuring some clear, easy-to-read code. The dependencies you’ll want may be put in by operating npm set up –save apollo-boost react-apollo graphql-tag graphql.

Right here’s an summary of what these dependencies are:

apollo-boost: a zero-configuration manner of getting began with GraphQL in React/React Native
react-apollo: this gives an integration between GraphQL and the Apollo consumer
graphql-tag: a template literal tag that parses GraphQL queries
graphql: the JavaScript reference implementation for GraphQL

As soon as all the essential dependencies have completed putting in, run npm begin. It’s best to now see your acquainted Expo window, and if you happen to launch the app (both by way of a simulator or on a tool) then it is best to see a display just like this:

A mockup of our getting started page

In primary phrases, this utility has two screens which can be managed by react-navigation, Dwelling.js and CoffeePage.js. The Dwelling display accommodates a easy FlatList that renders all the espresso beans provided to its knowledge subject. When clicked on, the consumer is navigated to the CoffeePage for that merchandise, which shows extra details about the product. It’s our job to now populate these views with attention-grabbing knowledge from GraphQL.

The complete coffee page

Apollo Server Playground

There are two major components to any profitable GraphQL transaction: the server holding the info, and the front-end question making the request. For the needs of this tutorial, we aren’t going to begin delving into the fantastic world of server-side code, so I’ve created our server for us able to go. All you want to do is navigate to in your favourite browser and depart it operating all through the course of improvement. For these , the server itself is operating utilizing apollo-server and accommodates simply sufficient code to carry the info we’d like and serve it upon receiving an applicable question. For additional studying, you may head over to to learn extra about apollo-server.

GraphQL Question Fundamentals

Earlier than we get into writing the precise code that’s going to request the info we’d like for our espresso bean comparability app, we should always perceive simply how GraphQL queries work. Should you already understand how queries work or simply wish to get began with coding, you may skip forward to the subsequent part.

Word: these queries gained’t work with our codesandbox server, however be happy to create your individual at if you happen to’d like to check out the queries.

At its easiest stage, we will use a flat construction for our queries once we know the form of the info we’re requesting:

{ }

On the left, we see the GraphQL question requesting the mix subject from espresso. This works properly once we know precisely what our knowledge construction is, however what about when issues are much less clear? On this instance, mix returns us a string, however queries can be utilized to request objects as properly:

{ {
blend: “smooth”


Right here you may see we’re merely requesting the beans object, with solely the sphere mix being returned from that object. Every object within the beans array might very properly include different knowledge apart from mix, however GraphQL queries assist us request solely the info we’d like, chopping out any additional info that’s not essential for our utility.

So what about once we have to be extra particular than this? GraphQL gives the aptitude for a lot of issues, however one thing that permits for terribly highly effective knowledge requests is the flexibility to go arguments in your question. Take the next instance:

{ {
espresso(companyId: “2”) “espresso”: ,

blend: “smooth”


What we see is that we will go an argument — on this case, the companyId — which ensures that we’re solely returned beans from one specific firm. With REST, you may go a single set of arguments by way of question params and URL segments, however with GraphQL querying each single subject, it may possibly get its personal set of arguments. This enables GraphQL to be a dynamic resolution for making a number of API fetches per request.


Thus far, all of our queries have had the fields of the returned object match the identify of the sphere within the question itself. That is nice when utilizing easy arguments, however what if you wish to question the identical subject with totally different arguments in your knowledge request? That is the place aliases are available. Aliases allow you to change the identify of a subject so you may rename any of the returned knowledge and subsequently use totally different arguments in your knowledge request. Take our espresso bean instance. What if we wished to return knowledge from two totally different firm IDs? We might construction our question like this:

{ {
company1: espresso(companyId: “1”)

Right here, we request knowledge for aliases company1 and company2, that are merely totally different espresso queries stacked on high of one another. Aliases generally is a highly effective software in modifying your requires on your precise knowledge requirement.


Up till now, we’ve identified our precise question and may subsequently hardcode it in our utility, however most functions will want these fields to be dynamic. As an example, the consumer would possibly choose a espresso bean firm from a listing to show. We gained’t know forward of time which espresso bean firm the consumer is choosing, so we’d like a manner of passing in these necessities. That is the place variables are available.

The GraphQL documentation lists three issues that we have to do with a view to use variables:

change the static worth within the question with $variableName
declare $variableName as one of many variables accepted by the question
go variableName: worth within the separate, transport-specific (often JSON) variables dictionary

In sensible phrases, this implies our knowledge question will look one thing like this:

question coffeeCompany(companyId: CompanyId)
espresso(companyId: companyId)

We might additionally go in companyId as a JSON object:

Utilizing variables inside GraphQL is a strong manner of constructing all of our question requests dynamic, as we’re requesting solely the info we presently want.

Espresso Question

For the needs of our utility, we’re going to want a question that permits us to request knowledge retrieving solely our espresso beans, while together with all the related fields we’re going to want inside that. Our knowledge necessities aren’t that complicated, so it can look one thing like this:


Requesting our Knowledge

Now for the precise code that we’re going to make use of to request our knowledge. Open up App.js, which is the container for all of our views and will likely be a very good place to make our knowledge request when the app launches.

We’re going to wish to initialize our consumer, which we will merely do by importing ApolloClient from apollo-boost and specifying our server URL. It’s necessary to notice that you want to have the server initialized, which is achieved by merely operating in your browser. Sometimes you would possibly discover the server timing out. If Expo returns a warning that appears one thing like “community error”, reload in your browser to re-initialize the server.

As soon as the server is operating, add the imports and initialization to the highest of App.js, which ought to look one thing like this:

// ./App.js
import ApolloClient from ‘apollo-boost’;

const consumer = new ApolloClient()

Subsequent, we wish to assemble the graphQL question for later use once we request our knowledge. Fortunately, the graphql-tag library makes this straightforward. Once more, we have to import the library itself to App.js:

// ./App.js
import gql from ‘graphql-tag’;

Now we will construction the question:

// ./App.js
const QUERY = gql`



The subsequent step is to amend the render operate to incorporate our knowledge request. To do that, we use the react-apollo library to make the request, which permits us to deal with the response as we see match. Add a brand new import to App.js:

// ./App.js
import from ‘react-apollo’;

Then change the render operate in order that it now seems like this:

// ./App.js
render() {
return (


Right here, you may see we’re utilizing the QUERY we created earlier to request the required knowledge. At this second in time, we’re merely rendering an empty view while loading, and if there’s an error within the knowledge request. In observe, this is able to be swapped out for the related loading and error views, however for this instance we’ll depart them clean. As soon as knowledge is returned, we’re rendering our AppContainer as typical. You may verify that knowledge is coming by means of by checking that knowledge is being returned efficiently. This may be checked by including a console.log(knowledge) to your code to view the output in your terminal. You need to be receiving an object with our espresso and beans fields so long as your Apollo server is operating with out a downside.

Storing Knowledge with the Context API

We’re going to want someplace to retailer our knowledge that will likely be accessible in any of our parts irrespective of how far down the tree they’re. If we have been to go the info throughout a number of youngsters simply to get to our element, that wouldn’t be essentially the most environment friendly factor. Provided that our knowledge storage wants are pretty easy for this instance, it might be good to make use of React’s Context API fairly than some extra complicated state administration software like Redux. The Context API allows you to go world state down our element tree with out the necessity for passing it by means of props every time, and for our present instance, that is sufficient.

The advantages of Redux on high of the Context API can broadly be narrowed down to a few factors:

Redux comes with a time touring debugger
it gives the developer with middleware APIs, supplying you with entry to instruments like redux-sagas
its React bindings stop having too many renders

Utilizing the Context API couldn’t be easier. In essence, we simply have to create a element to retailer all of our knowledge in and entry the info by making a element once we come to want it.

Making a Supplier

Let’s return to App.js, the place we solely have so as to add a few traces to get our Supplier up and operating. First, we’ll begin off by creating our AppContext. We’ll have to entry this in any file the place we wish to use the saved knowledge, so we’ll want to ensure it’s exported. To create the AppContext, add the next line to App.js:

// ./App.js
export const AppContext = React.createContext();

Right here, we’re creating the context and initializing it with some clean knowledge. Subsequent, we wish to populate the AppProvider with the info we’re receiving from the GraphQL server.

Storing cCoffee Knowledge

To replace our supplier with the info, we merely have to vary out the clean container view in our App.js render operate for the supplier while including our GraphQL knowledge to its knowledge prop. This seems like this:

// ./App.js
render() {
return (

() =>


Right here, you may see that we’re immediately storing the bean knowledge (knowledge.espresso.beans) in our supplier. At this level we’ve got all the knowledge essential, however we’re nonetheless rending our placeholder content material. The ultimate piece of this puzzle is to amend Dwelling.js to render our knowledge by utilizing a Client.

Creating an App Client

Firstly, we have to import our AppContext from earlier to utilize the Client. To do that, we merely have to import it from App.js into Dwelling.js:

// ./src/Dwelling.js
import from ‘../App’;

Utilizing a Client works like another React element. For our present functions, we’ll add it to our render operate and use the info to populate our FlatList. Our render operate ought to look one thing like this:

// ./src/Dwelling.js
render() {
return (

(context) =>






If we undergo the above code, you may see the AppContext.Client gives us with a context, which accommodates our GraphQL knowledge. We use this context to populate the FlatList element by passing it to the info prop. When the consumer clicks on one of many espresso gadgets, our knowledge is handed by means of navigation params to our CoffeePage.js, permitting it to be accessed in that view. Should you now save your modified information and launch the App on Expo, it is best to see your absolutely populated FlatList.

The finished App


Congratulations! You’ve efficiently used GraphQL to retrieve knowledge and render that knowledge utilizing React Native. We’ve discovered how highly effective GraphQL queries may be, while highlighting the advantages over a system like REST. I encourage you to make use of GraphQL in your subsequent mission and choose for your self how a lot faster it may be for retrieving knowledge — notably in data-rich functions.

If you wish to discover GraphQL in additional element, I like to recommend you learn the “Queries and Mutations” part of the GraphQL docs, and maybe begin coding an Apollo Server your self utilizing

The complete code for this mission may be discovered on GitHub, so be happy to clone/fork the repo and make your individual enhancements!

Jamie Maison

Freelance Software program Developer specialising in creating dynamic experiences for internet, cell and desktop. Learn extra at

Leave a Reply