Need help with react-native-template?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

145 Stars 66 Forks MIT License 64 Commits 4 Opened issues


A starter project for a React Native app

Services available


Need anything else?

Contributors list


The goal of this project is to work as template for react-native applications, providing a base project structure, core dependencies and boilerplate to jumpstart development.


Base dependencies


Use Template button

Click the "Use this template" button above the file list, then use the Owner drop-down menu, and select the account you want to own the repository. Creating a repository from a template has the following advantages:

  • A repository created from a template starts with a single commit.
  • Commits to a repository created from a template do appear in your contribution graph.
  • Creating a repository from a template starts a new project quickly.

Option #1: Using React-Native-Rename

You can start by cloning this repository and using react-native-rename. In the current state of this project, it should give you no issues at all, just run the script, delete your node modules and reinstall them and you should be good to go.

Keep in mind that this library can cause trouble if you are renaming a project that uses

on the iOS side.

After that you should proceed as with any javascript project: - Go to your project's root folder and run

npm install
. - Create a
file to store all your configuration constants. Remember to not commit this file, since it can store sensible information of your product. - Run
npm run ios
npm run android
to start your application!

Option #2: Copy the structure to your project

If you want to roll on your own and don't want to use this as a template, you can create your own project and then copy the

folder (which has all the code of your application) and update your

Keep in mind that if you do this, you'll have to install and link all dependencies (as well as adding all the necessary native code for each library that requires it).

Folder structure

This template follows a very simple project structure: -

: This folder is the main container of all the code inside your application. -
: This folder contains all actions that can be dispatched to redux. -
: Asset folder to store all images, vectors, etc. -
: Folder to store any common component that you use through your app (such as a generic button) -
: Folder to store any kind of constant that you have. -
: Folder to store all your network logic (you should have one controller per resource). -
: Folder to store the languages files. -
: Folder to store the navigators. -
: This folder should have all your reducers, and expose the combined result using its
: Folder that contains all your application screens/features. -
: Each screen should be stored inside it's own folder, and inside it a file for its code and a separate one for the styles and tests. Then, the
is only used to export the final component that will be used on the app. -
: Folder to store your selectors for each reducer. -
: Folder that contains the application storage logic. -
: Folder to put all redux middlewares and the store. -
: Folder to store all the styling concerns related to the application theme. -
: Main component that starts your whole app. -
: Entry point of your application as per React-Native standards.

Splash screen customization

To customize the splash screen (logo and background color) use the CLI provided in the official docs.

Setup environments

Add the environment variables files in root folder(.env.staging and .env.production)


A map associating builds with env files is already defined in

you can modify or add environments if needed.

For multiple enviroments to work you would need to change

-keep class [YOUR_PACKAGE_NAME].BuildConfig { *; }


The basic idea in iOS is to have one scheme per environment file, so you can easily alternate between them.

Start by creating a new scheme:

  • In the Xcode menu, go to Product > Scheme > Edit Scheme
  • Click Duplicate Scheme on the bottom
  • Give it a proper name on the top left. For instance: "Production"
  • Then edit the newly created scheme to make it use a different env file. From the same "manage scheme" window:

Expand the "Build" settings on left - Click "Pre-actions", and under the plus sign select "New Run Script Action" - Where it says "Type a script or drag a script file", type:

echo ".env.production" > /tmp/envfile
replacing .env.production with your file


For coding styling we decided to go with ESLint and React Native community's styleguide.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.