Portals need to undergo the same process as a standalone app, except a portal will need to be submitted with at least one project linked.
A Store Listing is the information submitted along with your Portal. This is required for all submissions.
Store Accounts must be created by your end-client prior to configuring the Store Listing and submitting the Portal.
A Store Account is required for Apps to be submitted. Note that each client/organisation you service will require their own Store Accounts.
Your end-client is solely responsible for ensuring their annual subscription is paid, and any privacy or other agreements are accepted. If their Store Accounts is not appropriately configured, Entegy will be unable to proceed with submitting the app, and delays will occur.
As an Entegy Partner, you are responsible for ensuring your end-clients are aware of their responsibilities with regards to configuring their Store Accounts.
Once your end-client has created their Store Accounts, they must provide you with their Store Account name. This is typically the legal name for the organisation, or the Team Name for Apple, and the Developer Name for Google. These details must be populated as a new Store Account in the CMS. This acts as a reference to the developer account and allows the Entegy Build Team to match the developer team invites to the CMS Store Account reference.
When the Store Account reference has been created in the CMS, this can then be added to the Store Listing.
Store Listing details appear as part of the App listing on the Apple App and Google Play stores. It is important to keep in mind that these details will be listed publically and should describe the App as much as possible.
The Store Listing consists of:
- Store Account name
- App Store Title
- Google Play Title
- Icon Title
- Short Description
- Design assets
All of these are required for the app submission to be successful. It is best practice to have your end-client complete the Store Listing details to ensure the information is correct etc.
Once the Store Listing details have been populated, it is important to confirm the app meets the requirements for both Apple and Google. These requirements include:
- Content behind each icon - no empty pages
- Menu items must not link to ‘coming soon’ message
- Completed app design and colours
- App Access Type: Public Access - no profile login
These requirements are further explained in this article.
If the app is ready and meets all the requirements, it can then approved for submission.
If an app is submitted prior to checking and does not meet the requirements, it will be rejected by the Entegy Build Team, and delays will occur.
The steps below outline the process of configuring the store listing in the Core (CMS) and submitting the portal. This will need to be completed by the partner.
Setup Store Listing Configuration
Once your client's Store Accounts have been created for the Apple and Google Play Stores, and team invites sent to Entegy, you will need to link these accounts to the Entegy CMS. These will create a single Store Account for your standalone app or portal.
Each portal must be submitted along with at least one (1) project. This project will need to need to avoid some common issues that cause apps and portals to be rejected. Entegy's recommendations allow not only the Entegy Builds team, but both Apple and Google to easily access and review your app and portal for submission.
A Store Listing is for portals which are to be submitted within the Google Play and Apple App stores. The submission process can take a few weeks. It's best to allow four-to-five weeks to create your store account with Apple and an additional two weeks to complete the submission process prior to your App launch.
Once you have fully prepared your Store Listing, the next step is to approve the App Submission.