Android Publishing (Local)

Learn how to manually publish your app to Google Play

Publishing your app to the Google Play Store might seem complex, but this guide will walk you through each step in simple terms. Don’t worry if you’re not familiar with technical concepts – we’ll explain everything along the way.

Prerequisites

Before you can publish your app, you’ll need to set up a few accounts and install some software. Think of these as the basic tools you need:

Required Accounts

Expo Account - This is a free service that helps build your app. It’s like having a construction crew that specializes in mobile apps.
Google Developer Account - This costs $25 one-time and allows you to publish apps on Google Play Store. Think of it as your business license to sell apps.

Required Software

Node.js - This is a tool that helps run the code needed to build your app. Download the “LTS” version (which stands for “Long Term Support” - the most stable version).
Git - This helps manage your app’s code files. It’s like a filing system for programmers.

Using the Console

Throughout this guide, you’ll need to use something called a “console” or “terminal.” This is a text-based way to give instructions to your computer. Don’t worry - it’s easier than it sounds!

Finding Your Console

Press Command + Space Command + Space Command + Space to open Spotlight search
Type “Terminal” and press Enter
A black or white window will open - this is your console

What is EAS?

EAS (Expo Application Services) is like a specialized factory for mobile apps. Instead of needing complex software on your computer, EAS builds your app in the cloud (on Expo’s powerful computers) and then gives you the finished product.

Think of it this way: instead of baking a cake in your kitchen, you give the recipe to a professional bakery, and they deliver the finished cake to you.

Install EAS CLI

First, you need to install a tool that lets you communicate with EAS. This tool is called “EAS CLI” (CLI stands for “Command Line Interface” - basically a way to give text commands to your computer).

Install EAS CLI

Open your console (see instructions above) and copy-paste this command, then press Enter:
Terminal window
```
npm i -g eas-cli
```
This downloads and installs the EAS tool on your computer. The process might take a few minutes.
Sign in to Expo

After installation, you need to log in to your Expo account. In the same console window, type:
Terminal window
```
eas login
```
The console will ask for your Expo username and password. Type them and press Enter after each one. Don’t worry if you can’t see the password as you type - this is normal for security reasons.

Download Your Project

After building your app in Draftbit, you’ll have a folder containing all your app’s code. Here’s how to prepare it:

Download and Open Your Project
1. Download your app’s code from Draftbit
2. Extract the ZIP file to a location you’ll remember (like your Desktop or Documents folder)
3. You can open this folder in a code editor if you have one (like VS Code), but it’s not required
Navigate to Your Project in the Console

You need to tell the console where your app files are located. In your console:
1. Type cd (that’s “cd” followed by a space)
2. Drag your project folder from your file manager into the console window
3. Press Enter
Your console should now show the path to your project folder.
Install Project Dependencies

Dependencies are like ingredients your app needs to work properly. Install them by typing:
Terminal window
```
npm install
```
This downloads all the necessary components for your app. It might take a few minutes.
Check Everything is Working

Run this command to make sure everything is set up correctly:
Terminal window
```
npx expo-doctor --check
```
This is like a health check for your app. If it finds any issues, it will suggest how to fix them.

Set Up Your Project

Before publishing, you should customize your app’s name and other details.

Updating Your App Name
1. In your project folder, find a file called app.json
2. Open it with any text editor (even Notepad works)
3. Look for a line that says "name": "..." and change the text between the quotes to your app’s name
For example:
```
"name": "My Shopping List App"
```
Setting Your App Slug

The “slug” is like your app’s unique identifier. It should be lowercase with no spaces:
```
"slug": "my-shopping-list-app"
```
Important: Once you publish your app, you can’t change the slug, so choose carefully!
Initialize EAS for Your Project

In your console, run:
Terminal window
```
eas init
```
This connects your project to EAS. You’ll be asked to choose which Expo account should own this project. Use the arrow keys to select your account and press Enter.
Configure EAS Build

EAS Build is the service that actually creates your app file. Think of it as setting up the assembly line in that app factory we mentioned earlier.

In your console, run:
Terminal window
```
eas build:configure
```
This sets up the configuration for both Android and iOS. You’ll see some text appear - this is normal and means EAS is preparing your project.

Deploy Your App

Now comes the exciting part - actually creating your app file and putting it on the Google Play Store!

Build Your App

In your console, run:
Terminal window
```
eas build -p android
```
This tells EAS to build an Android version of your app. The process happens in the cloud, so you can close your console and come back later if you want. You’ll receive an email when it’s done (usually takes 10-20 minutes).
Download Your App File

Once the build is complete, EAS will provide a link to download your app file (called an APK or AAB file). Download this file to your computer.
Upload to Google Play Console

Now you need to put your app on the Google Play Store:
1. Go to Google Play Console and sign in
2. Click “Create app” and fill in your app’s details
3. Navigate to “Testing” → “Internal testing”
4. Create a new release and upload the app file you downloaded from EAS
5. Add email addresses of people who should test your app
6. Publish the internal test
Test Your App

Google will provide you with a testing link. Share this with your testers so they can download and try your app before it goes public.

Go to Production

Once you’re satisfied with your testing, you can make your app available to everyone:

In Google Play Console, go to “Production”
Create a new release using the same app file
Fill in all required store listing information (descriptions, screenshots, etc.)
Submit for review

Google will review your app (this can take a few days) and then make it available in the Play Store for people to download.

Need Help?

If you get stuck at any point, remember that Draftbit’s one-click publishing can handle all of these steps automatically. You can also find more detailed technical information in Expo’s deployment documentation.

Don’t be discouraged if this seems overwhelming at first - many successful app developers started exactly where you are now!