Launching your Mobile Community

This guide will tell you everything you need to do in order to launch your own community app with us on mobile.

​

 

Step 1. Configure your app βš™οΈ 🎨

First, you will need to have an idea of how you want your app to look. For that, you need to decide on your design assets, your logos and your preferred colour scheme. You can also test out your preferred menu structure, and make changes in real-time.

Step 2. Master the Disciple Console πŸ‘¨β€πŸŽ“πŸ‘©β€πŸŽ“

You can get started by beginning our Community Course on The Collective. Here, we breakdown the training into bite-size chunks covering the following topics:

After this, you will have the knowledge to begin making your app your own, and you can start prepping for launch. You will need to think about content strategy and we suggest getting a plan together for the first 3 weeks after launch. Our Content Checklist πŸ“‹ is a great place to start. 


​
Step 3. Set up your developer accounts πŸ“±πŸŽ

In order to release your app under your company’s name, you need to set up developer accounts with Apple and Google Play. It’s a requirement from Apple that you need to be a registered legal company on Duns & Bradstreet in order to enrol into the Apple developer programme. If you are not a registered company, please look at this guide. Apple's enrollment process takes 3-4 days on average, but can occasionally take longer.

Once you have enrolled, you will need to link with our developer account so that we can manage the submission of your app for you. 

Step 4. Take care of your Privacy Policy βš–️ πŸ”

Because you have full control of the data in your community, you will need to be registered as the data controller for your app. In the UK, you must be registered with the Information Commissioner's Office (ICO). It costs Β£35 and it takes a day or so to process. The ICO requires a trading registration, whether as a sole trader or a company.
​
If you're outside the UK, you will need to check the data protection framework in your country to ensure you have sufficient cover in order to act as a data controller.
​
As the registered data controller you will be responsible for your app's privacy policy covering your community.  

To help make this a bit easier, we have drafted a template that you can review and use as a starting point. You will need to provide an email address and contact details where members can reach out to you if they have any queries about your app. This can be filled out within the Legal Docs section of your Console.

Step 5. Monetise (or not) πŸ’°πŸ€‘

If you are planning on adding a subscription or in-app purchase to your community, please take a look at these guides.

 

Step 6. Prepare for submission πŸ“ β˜•

The two main App Stores - the Apple App Store and the Google Play Store work in different ways. In order for an app to be released in the Apple Store, it has to go through a review process.

It usually takes Apple 24-48hrs to review. Once Apple has approved your app, it can be released into the App Store. Google Play takes on average between 5-7 days to approve an app.
​
We will guide you through the submission process. You will need to prepare certain assets including screenshots and copy to include in your App Store pages. 

Step 7. Launch your app! πŸš€ πŸ™Œ

Once your app is approved, you can launch your app to your community. Check out our post-launch marketing guide here

​We'll look forward to seeing you in The Collective



__________________________________________________________________

Looking to create your own community app? Contact our Community Experts -  info@disciplemedia.com

Need help with your existing Disciple powered community? Contact our Customer Support team - help@disciplemedia.com


​