APP publishing methods

Updated 1 month ago ​by Bruno Trevisan Policelli

There are several ways to publish apps on Google Play and on the Apple Store. Here are some examples of the processes that can be executed in both stores in partnership with InEvent:

Requirements

  • App customization information filled in;
  • Open and valid stores on Google Play and Apple Store

Important deadlines

  • The publishing of your app might take up to 10 business days.
  • Subsequent updates (name change, splash image, or color) occur within 5 business days.
  • The deadlines do not depend on the chosen form of publication (direct or MDM)

APPLE STORE (IOS): What are the possibilities of publishing the app?

After filling all app customization information and opening your stores on the Apple Store as an individual person (Apple Store - Individual) or as a legal entity (Apple Store - Business) you must select the best form of publication of the App based on its Compliance + Technical Support (IT) + Operational Effort.

Those are the viable possibilities by the Global standard of the Apple Store and InEvent:

1) Direct publishing via InEvent with global access

If you give us global admin access (if InEvent has access and login with the user who opened the store), our team will be responsible for carrying out the APP development and publishing processes, such as downloading certificates, file creation and store upload.

2) Direct publishing via InEvent with admin access

If we do not have global access, we might receive an email created by the client granting us admin access. The client would need to follow this step-by-step: Adding users inside stores.

On this case, our team will be responsible for carrying out the App development and publishing processes, such as downloading certificates, file creation and upload.

3) File generation (IPA) with or without certificates (files exportation)

- Sending closed binary file (IPA) with certificates

If it is not possible for InEvent to receive access to the store, the client might send InEvent these 3 certificates:

  • Provisioning Profile Certificate (click here to learn more about it)
  • Distribuition certificate (click here to learn more about it)
  • Push certificate (p12) (click here to learn more about it)

We must receive the certificates externally via email and you (client) will receive the IPA file (binary in the format accepted by the Apple Store) developed based on the information registered in your InEvent Platform account so you can continue with the publishing.

InEvent will not perform the development of store default images; you (the customer) must develop all of them based on the sizes and formats authorized by the Apple Store.

Follow the link for more information: http://iosres.com/

- Sending closed binary file (IPA) without certificates

If it is not possible to receive access to the store for publication of the APP and the necessary certificates; InEvent will develop the IPA file (binary in the format accepted by the Apple Store) based on information entered in your InEvent Platform account and you (the customer) must associate all required certificates for publishing + signature key.

InEvent will not perform the development of store default images; you (the customer) must develop all of them based on the sizes and formats authorized by the Apple Store.

Follow the link for more information: http://iosres.com/

GOOGLE PLAY (ANDROID): What are the possibilities of publishing the app?

1) Direct publication via InEvent with global access

We should receive the login and password of the user who opened the store so we can:

  • Create the APK file (file format accepted by Google Play) based on the information entered on the platform;
  • Publish the APK file;
  • Upload the default images from the APP as requested in the store.

Our team will be responsible for carrying out the processes involving the development and publication of the App.

2) Direct publishing via InEvent with admin access

If we do not have global access, we might receive an email created by the client granting us admin access. The client would need to follow this step-by-step: Adding users inside stores.

On this case, the client must send us the API Key. Click here to read a guide of how to create the API Key.

3) File generation (APK) with or without certificates

- InEvent signature binary file (APK) delivery

If it is not possible to receive access to the store for publication of the APP; you (client) will receive the APK file (binary in the format accepted by Google Play) developed based on the information registered in your InEvent Platform account and our signature to continue the publishing.

InEvent will not perform the development of store default images; you (the customer) must develop all images based on the sizes and formats authorized by Google Play.

- InEvent Unclosed binary file transfer (APK)

If it is not possible to receive access to the store for publication of the APP; you (client) will receive the APK file (binary in the format accepted by Google Play) developed based on the information registered in your InEvent Platform account and not associated with any subscription to follow the publication.

InEvent will not perform the development of store default images; you (the customer) must develop all based on the sizes and formats authorized by Google Play and associate your developer signature.


How Did We Do?