Skip to main content
Mobile App 45 min read

How to publish the ChurchLinker app to the App Store & Google Play

This guide walks you through publishing the shared ChurchLinker app to both the Apple App Store and Google Play Store. It is written so that anyone can follow it, even with no technical background.

Before you start: what you will need

Think of this like publishing a book. Before your book can appear in a bookshop, you need to register as a publisher, prepare your manuscript and submit it for review. Publishing an app works the same way.

You will need:

  • An Apple Developer account, costing £99/year (~$99 USD). You sign up at developer.apple.com.
  • A Google Play Console account, with a one-time fee of $25 USD. Sign up at play.google.com/console.
  • A Mac computer for the iOS build (or use Expo's cloud service, so no Mac is needed).
  • An Expo account (free), the tool that turns the code into an app file.
  • About 2 to 3 hours the first time. After that, updates take about 15 minutes.
Good news: You do NOT need to know how to code. Expo does all the technical work. You are mainly doing account setup and filling in forms.

Part 1: Set up Expo (the tool that builds the app)

1

Create a free Expo account

Go to expo.dev and click Sign Up. Create an account with your email address.

Once signed in, you will see your Expo dashboard. Keep this tab open; you will need it later.

2

Install the EAS command-line tool on your computer

You need to install a small program called EAS CLI (EAS stands for Expo Application Services). This is what actually builds the app.

Open your computer's terminal (on Mac: press Cmd+Space and type "Terminal". On Windows: press Windows key and type "cmd").

Type this command and press Enter:

npm install -g eas-cli

Then log in to your Expo account:

eas login

It will ask for your email and password. Type them and press Enter.

3

Connect the ChurchLinker mobile code to your Expo account

In the terminal, navigate to the mobile app folder:

cd /path/to/churchCRM/mobile

Then run:

eas build:configure

This command links the ChurchLinker app code to your Expo account and generates a project ID. It will ask you a couple of questions; press Enter to accept the defaults.

Part 2: Set up your Apple Developer account

4

Register as an Apple Developer

Go to developer.apple.com and click Account at the top right.

Sign in with your Apple ID (or create one if you don't have one). Then click Join the Apple Developer Program and complete the £99/year payment.

Important: If this app represents your church (not a personal project), consider registering as an Organisation rather than an Individual. This requires your church's company number and a D-U-N-S number (free from Dun & Bradstreet). It looks more professional and makes it easier to add team members.
5

Create the app record in App Store Connect

Go to appstoreconnect.apple.com and sign in.

Click My Apps at the top, then the blue + button, then New App.

Fill in the form:

  • Platforms: tick iOS
  • Name: ChurchLinker (or your church name if white-label)
  • Primary language: English (UK)
  • Bundle ID: com.churchlinker.member, selected from the dropdown (you may need to create it first in the Identifiers section)
  • SKU: any unique text, e.g. churchlinker-member-app

Click Create. You will land on the app information page.

6

Fill in your App Store listing

This is the page people see in the App Store before downloading. Fill in:

  • Description: See the example text below
  • Keywords: church, Christian, faith, community, giving, prayer
  • Support URL: your church website or support email page
  • Marketing URL: churchlinker.com

Example description you can copy and edit:

Stay connected with your church community wherever you are. ChurchLinker brings together everything your church uses in one place: events calendar, sermon library, online giving, prayer requests and direct messages from your pastoral team. Sign in to access your church's personalised app experience.
7

Take screenshots (required by Apple)

Apple requires at least one screenshot for each device size. The easiest way is to use the iOS Simulator on a Mac.

You need screenshots for:

  • iPhone 6.7" (iPhone 15 Pro Max): required
  • iPhone 6.5" (iPhone 14 Plus): required
  • iPad Pro 12.9": required if you support iPad

To take them: run expo start --ios, press Cmd+S in the Simulator to save a screenshot to your Desktop.

Upload these in the App Store Connect → Screenshots section for each device size.

Part 3: Build the iOS app

8

Build the iOS app file using Expo

Back in your terminal (in the mobile folder), run:

eas build --platform ios --profile production

This command sends the code to Expo's servers, which build it into an .ipa file (the format Apple requires). It usually takes 10 to 20 minutes.

When it's done, Expo will show you a link to download the file, and will also give you the option to submit directly.

You don't need a Mac for this step! Expo's cloud servers do the building. You can run this command from any computer.
9

Submit the app to Apple

After the build finishes, run:

eas submit --platform ios

EAS will ask for:

  • Your Apple ID
  • Your App Store Connect App ID (find this in App Store Connect → your app → General Information, a 10-digit number)
  • Your Apple Team ID (find it in developer.apple.com → Account → Membership)

EAS will upload the app automatically. In App Store Connect, go to TestFlight; you should see the build appear after a few minutes.

10

Submit for App Review

In App Store Connect, click on your app, then click Prepare for Submission.

Choose the build you just uploaded, answer Apple's questions about:

  • Encryption: select "No" (the app uses HTTPS but no special encryption)
  • Content rights: select that you own all the content
  • Advertising identifier: select No

Click Submit for Review. Apple will review your app within 24 to 48 hours (often faster).

Apple will reject the app if screenshots are missing or if the description mentions features that don't work. Make sure your test church account is working before submitting, as Apple's reviewers will sign in and check. Create a demo church account at demo.churchlinker.com and provide those credentials in the review notes.

Part 4: Google Play Store

11

Create a Google Play Console account

Go to play.google.com/console and sign in with your Google account.

Pay the one-time $25 registration fee. This is a lifetime fee; you only pay it once.

Complete the account form: your name, address and whether this is a personal or organisation account.

12

Create the app in Google Play Console

Click Create app. Fill in:

  • App name: ChurchLinker
  • Default language: English (United Kingdom)
  • App or game: App
  • Free or paid: Free

Click Create app.

13

Fill in the Store listing

In the left menu, go to Store presence → Main store listing. Fill in:

  • Short description: (80 chars max) "Connect with your church: events, giving, sermons, prayer & more."
  • Full description: Use the same text as your Apple listing
  • Screenshots: Upload at least 2 phone screenshots (you can reuse the iOS ones)
  • Feature graphic: A 1024×500 px banner image. Use your church colours.
  • Icon: 512×512 px version of the app icon
14

Build the Android app file using Expo

In your terminal, run:

eas build --platform android --profile production

This builds an .aab file (Android App Bundle, the format Google requires). It takes 10 to 20 minutes.

15

Submit the Android app

Run:

eas submit --platform android

EAS will ask for a Google Service Account key. To create one:

  1. Go to Google Play Console → Setup → API access
  2. Click Create new service account and follow the link to Google Cloud Console
  3. Create a service account, download the JSON key file and save it as google-service-account.json in your mobile folder
  4. Back in Play Console, grant the service account Release manager role

EAS will upload the build. In Play Console, go to Production → Create new release to publish it.

16

Complete the Google Play setup questionnaires

Google requires you to fill in some forms before approving the app. Go through all the items marked with a red dot in the left menu:

  • App content: Answer questions about your app's target audience and content rating
  • Data safety: Declare what data you collect (user email and name; say "Account info")
  • Target audience: Select "18 and older"

Once all sections show green ticks, click Send for review. Google reviews usually take 1 to 7 days for new apps.

Part 5: How updates work (this is the clever part)

The ChurchLinker mobile app is built with Expo, which has a feature called OTA updates(OTA = Over The Air). This means most updates happen automatically, without going through the App Store at all. Think of it like how your phone's apps update automatically in the background.

🚀 OTA update (instant, no review)

Changes to what the app shows, including new screens, bug fixes, text changes and new features using existing APIs.

eas update --channel production

The app downloads the update automatically next time it launches. Takes about 2 minutes.

📦 Full build (requires App Store review)

Changes to native features, including adding a new camera permission, push notification setup changes or a major version number bump.

eas build --platform all --profile production

Then submit again. Review takes 24-48 hours (Apple) or 1-7 days (Google).

In practice: 95% of updates are OTA updates. You'll only need to submit a full build for major version upgrades (e.g., when upgrading to a new version of Expo), roughly every 6 to 12 months.

Quick checklist: are you ready to submit?

  • Apple Developer account created and paid (£99/year)
  • Google Play Console account created and paid ($25 one-time)
  • Expo account created and EAS CLI installed
  • eas build:configure run in the mobile folder
  • App record created in App Store Connect with name, description and screenshots
  • App record created in Google Play Console with store listing completed
  • Demo church account set up for Apple reviewers to test with
  • eas build --platform all --profile production run successfully
  • eas submit run for both platforms
  • Reviews submitted. Waiting for approval!

Need help?

We can walk you through any step on a call, or review your App Store listing before you submit.

Contact support
Accessibility
Text Size
High Contrast
Reduce Motion
Reading Width
Accessibility