Deploy Native Apps
Prerequisites
Before publishing to either Google Play or Apple App Store there are requirements and recommendations that need to be completed beforehand. These requirements are based on rules and guidelines set out by the Google & Apple Review process as well as limitations on available API features.
Publish Content. Demo content and empty apps will be rejected as incomplete by review teams, so ensure that real content is made available through the app.
Invite the review accounts. Both Apple and Google require demo access to content, so if you are publishing content to groups ensure that these accounts have access for the review process.
Setup Google Play store. Unfortunately the Google Play API does not currently support automating creation of new apps on Google Play. For new apps you will only need to carry out this step once. Once setup Raven will then be able to automate deployments and metadata. How to setup an on Google Play.
Create Screenshots
You are required to upload at least 3 screenshots per device type. To make this easy you can automate your screenshots from the app previews section. Simply click a screenshot placeholder and select automate screenshots and follow the prompts. Screenshot automation takes 1 - 3 mins to process per device. Of course you can also upload your own just remember to follow Google Play and App Store guidelines.
How to create screenshots for apps
In the App Editor, navigate to App Previews.
Upload screenshots or Create screenshots using Raven's Capture Screenshots.
If capturing screenshots, open the screenshot editor once the process is complete.
Set captured screenshot styles, text and colors.
Further Reading
Load Store Listing
The app's store listing (metadata) is attributes and properties that detail your app for the App Store and Google Play. During review processes metadata is the first step in the review process so it is important to provide clear and correct information about the app:
Description. The app description should have a summary of the app which includes: What features are available, who the audience is and what type of content is available. Ambiguous and unclear descriptions are likely to stall the review process as review teams will request further information, if the app’s intended purpose and audience is unclear.
Support & Marketing. Provide marketing URL which should be link for users to learn more about the app or company. The app's support URL and email for users to direct support queries and feedback.
Category & Tags. Provide a primary category for the list of available categories. These categories are predefined by Google Play and the App Store. The app tags should be keywords to help users find your app when searching app stores.
Primary Language. Select the primary language for your store listing. Raven doesn't support multiple language store listings but you can still create these manually if required.
Select Locations
Under locations select which countries you would like the app to be available in. We recommend selecting the minimal amount of countries for new apps and adding additional countries when needed. This is just good practice in app rollouts to manage user feedback and allow for any tweaks before releasing world wide.
Deploy (New Apps)
If the app is new, you will need to do a few once-off manual steps before deploying to production. This is due to some limitations outlined in the overview. Follow the steps below for Google Play and App Store:
Deploy Preview & Test. From the deployments section select the plus icon, this will open the deployment setup screen. Set the release as Preview for the App Store and Test for Google Play. Once set select deploy.
Setup Google Play. In step 1 open the deployment task for Google Play Test Release. You will see a download option for an AAB File. Download this file and follow the steps on How to setup Google Play.
Deploy Production / Preview. Once all steps are complete create a new deployment and select production or preview for all destinations. Production deployments will require a review for both Apple & Google Play which can take 1 - 2 days. Once approved you will be notified that the app has gone live.
Promote Preview. If you previously deployed preview version, you can promote these when you want to go live. Simply select the completed preview deployment and choose Promote Release to move preview releases into production. This will set the apps into review for App Store and Google Play which can take 1 - 2 days to approve.
Setup Apple Push Notifications (APNs) on Firebase. For new apps you will need to grant permission for Firebase to send notifications push notifications to devices view the Setup APN on Firebase Guide.
Deploy (App Updates)
Once an app has successfully deployed to production, subsequent production deployments are fully automatic. You will likely deploy an update when there is a new version of a blueprint or need to make icon or font changes to the app.
Updating Blueprint New blueprints will become available when patches are made or new features are added. You can update the blueprint from the App Editor or when Running Multiple deployments.
Deploy an update to single app Open the app on Raven and navigate to Deployments. Select the plus icon and deploy, once the process is finished your app will updated on App Store and Google Play.
Deploy an Update to multiple apps Open Raven and select the plus icon on the Apps Overview Dashboard. Select Run Multiple Deployments. Select the apps you want to update and click Deploy.
New Apps on Google Play
For new apps you will need to setup on Google Play manually first. After this process is complete you can automate android deployments.
Download AAB File. Once you have created a test deployment on Raven for Android download the AAB / Android App Bundle.
Create App listing on Google Play Console. Add a new app and fill in the initial setup which includes the name, language (en-GB) and declarations.
Setup Main Listing. Add store listing information such as icon, feature banner, descriptions and categories.
App Content. Complete all the sections especially Data Safety and App Access. You can import the Data Safety settings from the Data Safety for Google Play link found in Raven under Policy & Content. For App Access provide the default demo account or specify an alternative.
Create Closed Track. Create a new release in the Closed Testing section. Set the locations and upload your AAB file you download from Raven earlier. Once complete release the track.
Wait for Review. Before deploying or promoting to production from Raven, wait for Google Play to approve your manually setup. Once approved you can safely automate promoting and production deployments for android on Raven.
Following Apple's Guidelines & Policies
All Apple apps go through a human-led App Review process. Licensees publishing multiple apps must ensure that each app is differentiated from the next. If the review team notices similarities between apps submitted, an app may fail the Spam app guideline and will not be published.
4.3 Spam Guideline (a)ASR & NR Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase.
To circumvent app rejections, please ED's app publishing policy requires that the following guideleines be met:
Design. Each app must be identifiably unique. Do not use similar branding elements or colors that have been published in your developer account.
Content. Ensure that content is unique to the app. Do not reuse the content of apps that have been published in your developer account.
Meta Descriptions. The first part of the review is reviewing the meta descriptions. Ensure this is unique app to app, and provides the specific industry, audience, and topics.
Last updated