It can be overwhelming to think about all you have to do to launch your mobile Community. This guide will tell you everything you need to do in order to have a successful launch.
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.
- What creative assets do I need to get started?
- How do I decide my menu structure?
- How do I edit my menu?
Master the Disciple Console:
We have some incredible resources on our own Community platform called The Collective. Here you can access video and written resources alongside speaking to your peers about how to best help your Community thrive.
We also have some essential reading below to help you get started from our fantastic knowledge base:
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.
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. Apple's enrollment process takes 3-4 days on average, but can occasionally take longer.
Once you have enrolled, you will need to link Disciple Media with our developer account so that we can manage the original submission of your app for you.
- How do I set up a developer account on Google?
- How do I set up a developer account on Apple?
How do I link my developer account with Disciple?
To make this a bit easier, we have drafted a template that you can review and use as a starting point. Access these by heading to your Console, clicking on Configure from the left hand menu and selecting Legal Docs.
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 which can be filled out in the docs themselves.
However, 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.
To Monetise (or not):
If you are planning on adding a subscription or an in-app purchase to your Community, please take a look at this guide:
- Setting up your Developer Account for subscriptions
- You will then be asked to fill out a form, which you can do here.
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, it has to go through their review process.
It usually takes Google an average of 5-7 days to approve an App, whilst it generally takes Apple 24-48 hours. Once approved, your App can be released into the Google Play and App Stores.
We will guide you through the submission process, but you will need to prepare certain assets including screenshots and a copy to include in for the Google Play and App Stores.
- What do I need to prepare for the Google Play Store?
- What do I need to prepare for Apple's App Store?
A detailed guide to App Store Optimisation
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 cannot wait to see your incredible new Community!
PS. Don't forget you can always reach out to our amazing Support team if you ever need any help by emailing email@example.com.