App publishing methods

There are several ways to publish apps on Google Play and on the Apple App Store. Here are the options available to you that can be executed in both stores in partnership with InEvent:

What options do I have regarding having my app published?

These are the viable possibilities by the Global standard of the app stores and InEvent.

1) Direct publishing via InEvent with global access

This is the recommended option for optimum app publishing.

This options equips InEvent with identical access and login details with the user who opened the store.

To do this, simply input this information in your Company Details page.

InEvent's team will be responsible for carrying out the app development and publishing processes, such as

• Downloading certificates
• File creation and store upload, and
• For the Google Play Store,
  • Create the APK file (file format accepted by Google Play) based on the information entered on the platform,
  • Publish the APK file and upload the default images from the APP as requested in the store.

2) Direct publishing via InEvent with admin access

If InEvent do not have global access, we can 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.

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

For the Google Play Store, you must send us the API Key. Click here to read a guide of how to create the API Key.

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

This section is divided per platform.

Apple App Store

Sending closed binary file (IPA) with certificates

If it is not possible for InEvent to receive access to the store, you are required to send InEvent these 3 certificates:

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

We must receive the certificates externally via email and you 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 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 must associate all required certificates for publishing + signature key.

InEvent will not perform the development of store default images; you 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 Store

InEvent signature binary file (APK) delivery

If it is not possible to receive access to the store for publication of the app; you 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 must develop all images based on the sizes and formats authorized by the Google Play Store.

InEvent Unclosed binary file transfer (APK)

If it is not possible to receive access to the store for publication of the app; you 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 must develop all based on the sizes and formats authorized by Google Play and associate your developer signature.