Mobile App Submission: Android Store Listing Settings
Configure the information that appears on the product page for your mobile app in the Google Play App Store.
This must be filled in. If this information is not filled in, we cannot submit the app for approval and release.
Appearance
- Configure the information that appears on the product page for your mobile app in the Google Play Store.
- Notification Icon: Dimensions: 96px by 96px square
- Format: PNG with a transparent background
- Requirement: Icon design must be solid white
- Appears in the device status bar, notification menu, and lock screen.
- Will use mobile app icon if not provided.
- Warning: Stock images requiring attribution cannot be used here
Configure the information that appears on the product page for your mobile app in the Google Play Store.
- Contact Email: This email address is publicly viewable in the app store.
- Feature Graphic: Dimensions: 1024px by 500px
- Format: JPEG or 24-bit PNG with a solid background (no transparency)
- Recommended: Typically used to display your station logo with a branded graphic.
- Appears at the top of the product page for your mobile app in the Google Play Store and may be featured anywhere within the Google Play Store.
- Will use mobile app icon if not provided.
- Warning: Please make sure your descriptions and images do not include promotional marketing copy, e.g. “Toronto’s Number 1 Station”.
- Warning: Stock images requiring attribution cannot be used here
Credentials
Configure the credentials required to build and submit your mobile app.
- Credentials: Choose 1 of the android integrations you set up earlier. If you have not setup an integration already, click the 'manage credentials' or 'add new' buttons.
Version
Configure the version information for your mobile app build.
- Check yes, to replace an existing mobile app in the Google Play App Store instead of creating a brand new app.
Keystore File
Configure the keystore file that is used to uniquely identify you as the owner of your current mobile app. This is required to replace your existing Android app or to move your app to another app developer.
- Allow your mobile app to be moved to a different app developer in the future. SoCast will create a new keystore file for you for a one time cost. A SoCast client success manager will contact you for billing details before proceeding.
- Upload an existing keystore file from a previous mobile app developer or one that you created yourself. (this allows us to replace your existing app, from your previous app developer)
Related Articles
Mobile App Submission Store Listing Settings: General Store Information, App Icons, Ratings, Privacy Etc
Configure the appearance of your mobile app in the Apple App Store, Google Play Store, on user devices, and within the app. These are the general settings, you will need to fill in specific settings for both iOS and Android. Appearance App Store ...
Mobile App Submission: iOS Store Listing Settings
Configure the information that appears on the product page for your mobile app in the Apple App Store. This must be filled in. If this information is not filled in, we cannot submit the app for approval and release. Store Information Promotional ...
Mobile App Submission / Build Checklist
The following configurations must be completed to build and submit your mobile app to the Apple App Store and Google Play Store. We cannot submit an app build unless all fields are complete and filled out as per the specifications. We highly suggest ...
Accepting Agreements In App Store
Log into App Store using Admin credentials Select “My Apps” icon Select “Agreements” in the header menu Select on the outstanding agreement and agree to its terms Contact SoCast that the agreement has been accepted
Why Does Google Play Say The App Isn't Available In My Country?
This Article Is For: Users who have been given permission to manage Mobile App Settings This is applicable to: Single Tenant App & Multi-Tenant App Requirements: Station/brand have already purchased the SoCast Mobile App package Have been given the ...