Exporting Your Project
In order to export or publish your Draftbit app, you will need the following tools installed on your local machine:
- Expo CLI
- Watchman for macOS users
- Yarn use this over
npm installwhen installing dependencies
- EAS CLI
Only Node.js LTS releases (even-numbered) are recommended. As Node.js officially states, "Production applications should only use Active LTS or Maintenance LTS releases."
You can install Node by going to the website directly and clicking the side that says "Recommended For Most Users". This will guide you through the process.
Once Node has been installed, run the following on the command line to make sure
it's been installed correctly:
$ node -v
If you see the current version of Node in response, you've successfully
installed Node on your machine.
$ node -v v14.17.3
Learn more about installing Nodejs
Installing Expo CLI
You can install the Expo CLI using the following command. This is the one spot where npm install is required!
$ npm install -g expo-cli
Verify that the installation was successful by running
expo whoami. You're not logged in yet, so you will see "Not logged in". You can create an account by running
expo register if you like, or if you have one already run
Learn more about Expo CLI here.
Installing EAS CLI
Later on, when you will be publishing your app for iOS and Android app stores, you will require to use a service created by Expo called EAS.
EAS Build is a service that takes everything good about the Expo build service
(expo build:[ios|android]) and makes it available to all React Native apps.
Open the terminal window and run the following command to install the EAS CLI.
npm install -g eas-cli
Make sure to login into your EAS account from the terminal by running the command
eas login. It will ask for your Expo account's credentials.
Learn more about EAS CLI here.
Add your Bundle Identifier
Before exporting your app, make sure to modify three properties in Project Settings:
- slug: used to refer to your app. It is often in the format
- iOS Bundle Identifier: also known as bundle ID is used to uniquely identify an application in Apple's ecosystem. It is of the format
- Android Package Name: used to uniquely identify an application in Google's ecosystem. It is of the format
Make sure to only include letters, numbers, periods(.), and hyphens (-) in your identifiers. Also, make sure it's in reverse-DNS format. Read more about that here.
Export Your Project
Once you've built your app, it's time to export your project out of Draftbit and onto your own machine. Click Code from the top bar and then click "Export App".
After clicking the Export App button, you will receive an email from Draftbit (at the email registered with your Draftbit account). In the email, you will find the link to download the source code of your Draftbit app.
Alternate way of Exporting your app: Using GitHub
If you are already using GitHub to commit your Draftbit app's source, code you can also export it from there. Learn more here on how to commit your Draftbit app's source code to a GitHub repository.
Install Project Dependencies
First, navigate to the project directory. The
.zip will likely be in your downloads folder, so extract the
.zip and move it to the desired location before proceeding.
Now, run the following commands to install the project dependencies (note that you'll need an internet connection to do so).
cd Desktop/draftbit-app yarn
cd command above takes you into the project directory so you can install the correct dependencies. You should replace
Desktop/draftbit-app with the actual path to your unzipped project folder.
Post steps after exporting your app
Modifying the name and description of your app
To modify the name and description of your app, open the app project folder in a code editor. Then, open the file
app.json in the editor.
- Inside this file, to modify the name of your app edit the value of the property
- To modify the description of your app, edit the value
Setting up your app version
You can also set the versioning of your app for each platform.
- The property
app.jsondetermines the overall version of the app.
- In addition to this field, you can also set
Later, when you are updating your app and releasing those updates to the app store, you can increment the values for these versions related properties.
Running Your Project Locally
This step is not required in order to build the iOS and Android binaries for your app and submit to the app store.
The fastest way to get up and running is to use the Expo Go app on your iOS or Android device. Expo Go allows you to open up apps that are being served through Expo CLI by scanning a QR code.
- 🤖 Android Play Store - Android Lollipop (5) and greater.
- 🍎 iOS App Store - iOS 11 and greater.
To run the project on your local machine, you need to execute the command below:
This should open the Expo developer tools in a browser tab. It will give you a QR code to scan to view your project on your phone.
Additionally, you can click
Run on Android device/emulator or
Run on iOS simulator and Expo will start the project in Android Studio or XCode if they are installed on your computer.
The QR code will also be generated in the terminal along with a menu of options.
Running on a simulator/emulator
You can run your app on your mobile device, on the iOS simulator (if you have a Mac), or on the Android emulator. If you'd prefer to run your app on an emulator, see the installation instructions below.
Publishing your Project
To publish your project, run the command
expo publish in your project's directory in the terminal. You can read more on publishing in Expo's docs.
Expo has provided a list of best practices to follow when preparing your app for deployment that you may want to take a look at and confirm before you begin your app's build.
Updated 4 months ago