_(This article is part of an ongoing series on technical and soft skills from Nathan Thomas, a full stack software engineer studying and working at Lambda School based in Silicon Valley. Click_ [_here_](https://blog.usejournal.com/the-pursuit-of-persistence-and-grit-c13ad37743c4?sk=a77aba0333ab82b2369d46a97715f3c1) _for part 5 in the series, an article about “The Pursuit of Persistence and Grit.”)_

### Getting Started with React Native

It’s time for another to-do app tutorial!

Just kidding.

I can guarantee that this walkthrough will be worth your time, much like double-stuff Oreos or a happy golden retriever puppy. We’ll be building out a simple weather app in [React Native](https://facebook.github.io/react-native/) using [MetaWeather](https://www.metaweather.com/api/), a free weather API. React Native is a library for building iOS, Android, and most recently [Windows, tablets, and Xbox applications](https://techcrunch.com/2019/05/06/microsoft-launches-react-native-for-windows/).

Here’s an example of the [finished product](https://snack.expo.io/@nwthomas/react-native-app-demo) we’ll be making. I’ve even thrown in a higher order component and some light styling for some extra seasoning so you can see that React Native isn’t so crazy after all.

As always, I like to define my reader expectations up front; you need to be familiar with React, as I won’t be explaining concepts fundamental to it. In fact, your ability to quickly learn React Native from this article _depends_ on us being able to compare what we’re doing to how we would normally use React. Additionally, you need to be familiar with Flexbox and the basics of CSS. Lastly, it would also be great if you’re used to working with APIs, but it’s not a requirement; I’ll hold your hand through that part and give you the code for everything.

With that out of the way, let’s go ahead and get started. I think you’re really going to have fun with this one.

> _“We take better care of our smartphones than we do of ourselves — the phones are always recharged!”_

> _— Arianna Huffington_

### Let’s Make It Rain

There are just a couple things we need to do before we code anything. I’ll list them all out here:

1.  Go to the [Expo website](https://expo.io/) and sign up for a free account. Once you do, scroll down to the footer, look for a column labelled “Beginners,” and click on the “Try Expo Snack” link. Snack is a free, online code-editing sandbox for React Native, and it’s what we’ll be using today.
2.  I need you to go grab a cup of your favorite hot beverage. If we’re going to do this, we’re going to do it right. We’re going to get comfortable.

When you’re done with both of those things, create a new, blank project in Snack. Your new boilerplate app should look something like this:

![](https://cdn-images-1.medium.com/max/1024/1*S-uNWlP77VmUnxrojd5meg.png)

Snack makes up amazing names when you create a new application. Mine’s called “intelligent donut,” but yours might be something like “amused pistachio” or “frisky blueberries.” Go ahead and rename it if you want (although I’d personally keep either of those last two names), and then hit the big “Save” button in the top right corner. I’m going to call mine “React Native App Demo” for the sake of clarity during this walkthrough.

Go ahead and delete everything in App.js and paste in the following code:

<a href="https://medium.com/media/383fc891b3a4b19a0ddf0a0353e4b367/href">https://medium.com/media/383fc891b3a4b19a0ddf0a0353e4b367/href</a>

This is instantly going to throw an error because we haven’t created a HomeView component yet, but don’t panic from the red screen of death Snack is going to throw us. Let’s take a moment to discuss what’s going on with our code, and then we’ll go fix it.

Notice how I’ve only imported the react dependency so far. If this doesn’t prove to you that you can easily learn how to use React Native coming from a web background, I don’t know what will. We are running full-blown React on a mobile device, and we’ll supplement it in just a minute with the react-native dependency for anything else that needs to be tweaked to make it work.

With that little pep talk out of the way, go ahead and remove all the files in the existing components directory, add a container directory inside that one, and make a new HomeView.js file to go inside it. Paste in the following code (and then we’ll discuss it):

<a href="https://medium.com/media/1d18eadc3ba355b0b180404d04d588f4/href">https://medium.com/media/1d18eadc3ba355b0b180404d04d588f4/href</a>

Did you read through all of that? Good. You deserve a medal, high five, or at least a cookie 🍪 from someone. Go ahead and take a quick mental break to swig some of that hot beverage you’re holding.

Okay, let’s discuss what’s happening.

First off, we have the import line for react-native. It looks like this:

<a href="https://medium.com/media/161f9f3a557ec3213da1f0fe35a354b8/href">https://medium.com/media/161f9f3a557ec3213da1f0fe35a354b8/href</a>

These named exports from the react-native dependency allow us to build out our mobile application on top of normal React. But don’t be intimidated by them; they directly correlate to pretty much everything you already know about the web environment:

1.  Text is used the same way as the p, h1, h2, and all of those other sorts of text-containing tags.
2.  The View tag is used in much the same way as you would a div, section, header, footer, or other sorts of organizational tags in HTML.
3.  ScrollView is very much like View, but it’s _extra fancy_ 🎉 since it allows us to extend our container past the boundaries of the screen so that the user can swipe through content. We’ll see how this works in a bit.
4.  Finally, the StyleSheet import enables us to build out a complete stylesheet object inside of our application using CSS styles.

Taking that knowledge, let’s work our way down the page and analyze the code. To start, here’s the class in our HomeView.js component file:

<a href="https://medium.com/media/f26f6b9a5ebdce319562ced25357ec44/href">https://medium.com/media/f26f6b9a5ebdce319562ced25357ec44/href</a>

As you can see, we have our class structured with a ScrollView as the overall container. This allows us to have a scrollable, fluid structure to the page that the user can drag through with their finger. Inside of that, we have our View and Text tags which contains some text content. Finally, the last thing to note here is that we’re using _another_ Text tag inside of the first one; this functions (in this scenario) very much like if you had a span tag inside of a p tag in your JSX in normal React. It allows you to single out parts of the text for specific styling.

We have our StyleSheet below our class. As a reminder, this is what it looks like:

<a href="https://medium.com/media/873103a28a604bb895c4318c04908e14/href">https://medium.com/media/873103a28a604bb895c4318c04908e14/href</a>

When we call StyleSheet's .create() method, we can pass in an object that contains multiple key-value pairs of styling objects. React Native connects these to our component and makes them accessible for reference there.

In the code snippet, the scrollContainer style is assigned the value of an object with many individual CSS styling properties inside of it. These are all camel-cased (i.e. marginBottom and justifyContent), and any text value is wrapped in quotation marks (i.e. "center", "spaceBetween", etc.).

Additionally, notice that all measurements lack the values (i.e rem, px, etc.) that you know and love (and maybe hate) from a web environment. This is because all measurements in React Native default to plain integers without a unit type ending. These represent pixel-density-independent proportions on the screen.

This is also a great moment to talk about how layout work in React Native. I’ve previously said that CSS is the technique you use to style everything, but you’ll also be pleased to know that Flexbox is the module we use for all layouts. There are two significant differences with it that you need to know about right now, though:

1.  The CSS styling property of flexDirection in the Flexbox module defaults to column instead of row in React Native.
2.  The new flex property, shown in scrollContainer up above, sizes the element according to the number assigned to it. There is no way I can explain it in this small space better than the [official documentation](https://facebook.github.io/react-native/docs/layout-props#flex), so I highly recommend you give it a quick read.

As we previously said, the object passed into StyleSheet.create() applies to the component when it mounts. We then utilize the styles on it by writing style={styles.styleNameGoesHere} on the component in the code; here’s the HomeView.js class again so you can see what I’m talking about:

<a href="https://medium.com/media/f26f6b9a5ebdce319562ced25357ec44/href">https://medium.com/media/f26f6b9a5ebdce319562ced25357ec44/href</a>

Pretty cool, right?

Now that we have a basic grasp on some of the React Native imports as well as how the default stylesheets work, let’s go ahead and rig up a higher order component, some presentational components, and make an axios call to our MetaWeather API.

> “When we started work on the iPhone, the motivation there was we all pretty much couldn’t stand our phones, and we wanted a better phone.”

> — Jony Ive

### When It Rains, It Pours

At this point, your app should have the following image on screen and file setup as shown below:

![](https://cdn-images-1.medium.com/max/1024/1*jylGuZTw5-Xhs61MjY89jQ.png)

We’re going to go ahead and build out the rest of this app. I’m going to show you entire snippets of code to paste in, and we’ll talk about anything unique before we move on to the next one. Sound good?

First, create a LoginView.js component inside your container directory and paste in the following code:

<a href="https://medium.com/media/7cd1e1cb6f5daf04fb87de0829557548/href">https://medium.com/media/7cd1e1cb6f5daf04fb87de0829557548/href</a>

This only new thing I want to point out here is that we can import and use the prop-types dependency just like in normal React. We won’t be doing that in the rest of the application, but it’s important that you at least see it once. Now we have to go flesh out the rest of the app so that this component's buttonFunction will get passed in on props.

That code above is also going to throw a big red error due to the button import, so create a presentational directory inside the components one and make a Button.js file there. Paste in the following code:

<a href="https://medium.com/media/632b5603c500581f430744af6b649f60/href">https://medium.com/media/632b5603c500581f430744af6b649f60/href</a>

In this code, I want you to notice what we’re importing from react-native— TouchableHighlight is what allows React Native to respond properly to touches when wrapped around other tags. We have to supply it with an underlayColor prop and a hex color code (the last two numbers of the #0E30F050 above are the opacity percentage). If we don’t supply this, the color will turn super funky when we press the button (read about why [here](https://facebook.github.io/react-native/docs/touchablehighlight)).

Additionally, notice that we no longer have onClick events. Instead, we’re using onPress which seems super obvious if we stop to think about it. We are using smartphones, after all!

Our next step is to make one more file in your container directory. We’ll name it authenticate.js. This is a higher order component for an _extremely_ simple pseudo-login process. Paste this code in:

<a href="https://medium.com/media/0dd833be919505acd6c178aab8111f85/href">https://medium.com/media/0dd833be919505acd6c178aab8111f85/href</a>

The point of using a higher order component and some light currying is to show you that we’re flexing the exact same muscles as in normal React. React Native isn’t that bad, and things are really starting to come together now!

Obviously, we need to complete the circle with our components, and you can probably see where this is going if you’re used to currying and higher order components in React; let’s go back to App.js and update it to look like this:

<a href="https://medium.com/media/334b4fee5c66ab82c9349430857d8f0f/href">https://medium.com/media/334b4fee5c66ab82c9349430857d8f0f/href</a>

Right on! At this point, our file structure and application should look like this:

![](https://cdn-images-1.medium.com/max/1024/1*1AExyyLypGEi_jn2u9DxAg.png)

If you click that beautiful blue button, you will “login” to your application. It’s time to make our call to the MetaWeather API and display our data to the screen!

![](https://cdn-images-1.medium.com/max/1024/1*iGZbXNKBBAc_A7IPvOTPBw.jpeg)

Image by [Alfred Twj](https://unsplash.com/@alfredtwj) on [Unsplash](https://unsplash.com/)

### Excuse Me While I Kiss the Sky

First, go ahead and click on the package.json file. Delete all the code in there, and paste the following dependency list in:

<a href="https://medium.com/media/34ce9193aabaf9db14665d017692d597/href">https://medium.com/media/34ce9193aabaf9db14665d017692d597/href</a>

Isn’t it nice to know that we have ye olde package.json with us and along for the ride?

Next, go to HomeView.js and update the code to look like this:

<a href="https://medium.com/media/4a4229ffafc937b1cd19a72d8d1d9100/href">https://medium.com/media/4a4229ffafc937b1cd19a72d8d1d9100/href</a>

We just imported the axios dependency along with the Button.js component, added a class constructor function, implemented a componentDidMount() lifecycle method, but some new text and a button in our component code, and added a weatherText style in our StyleSheet code. The axios call happening in our lifecycle method is currently coded to San Francisco, but you can tweak it using the information in the MetaWeather API documentation [here](https://www.metaweather.com/api/).

Whew. 😰

That was a lot of work, but we’re all done! Poke your way around the application, and you’ll find that you can log in, drag the ScrollView page from HomeView.js around, render the current weather to the screen, and logout using the button on the home screen.

### Additional Resources for Your Journey

1.  [React Native official documentation](https://facebook.github.io/react-native/) — These are really well-written, and you can basically search your way through building an app (with some light sprinkling of Stack Overflow thrown in).
2.  [Expo](https://docs.expo.io/versions/latest/)— This is the premier way of building out a React Native application. They made the Snack software we used in this article. I used Apple’s raw Xcode on my last project since Expo doesn’t support React Hooks, and trust me, you should use Expo. There are some nice CLI tools to work locally on your computer so you don’t have to use Snack in the future.
3.  [React Router Native](https://reacttraining.com/react-router/native/guides/quick-start) — There are many choices out there for navigation in React Native, but this one is great since it uses the exact same syntax as React Router (except that it doesn’t have a NavLink).
4.  [Styled Components](https://www.styled-components.com/) — You can use this amazing styling library in React Native by installing the dependency styled-components and then importing styled-components/native anywhere in your app.
5.  [React Native Shadow Generator](https://ethercreative.github.io/react-native-shadow-generator/) — A great resource for generating cool drop shadows for your apps. I used this to generate the shadow on the welcome card in this article’s demo app.

Thanks for reading.

Nathan

([GitHub](https://github.com/nwthomas), [LinkedIn](https://www.linkedin.com/in/nwthomas-profile/), [Twitter](https://twitter.com/nwthomas_), [Instagram](https://www.instagram.com/nwthomas/), and [Portfolio Site](https://nathanthomas.dev/))

Apple

Facebook

Instagram

Instantly

Microsoft

Super

Techcrunch

Twitter

Winner of Noonies 2020 for the award Hacker Noon Contributor of the Year - Graphql.

Building Your First React Native App

Too Long; Didn't Read

Companies Mentioned

Coin Mentioned

@nwthomas

RELATED STORIES