---
title: Prepare your mobile app
description: Learn how to prepare and publish your first mobile app with inwink, from app configuration and developer accounts to testing and App Store and Google Play publication.
---

[Skip to content](https://help.inwink.com/préparer-son-app-mobile#main-content)

- [English](https://help.inwink.com/pr%C3%A9parer-son-app-mobile)
- [Français](https://help.inwink.com/fr/préparer-son-app-mobile)

English

Show submenu for translations

[More support](https://help.inwink.com/kb-tickets/new?hsLang=en)

[![logo inwink](https://help.inwink.com/hs-fs/hubfs/LOGO_RGB@600x-2.png?width=100&height=75&name=LOGO_RGB@600x-2.png)](https://help.inwink.com/?hsLang=en)

- [Knowledge base](https://support.inwink.com/)
- [My tickets](https://support.inwink.com/tickets)

Open main navigation

Close main navigation

- [Knowledge base](https://support.inwink.com/)
- [My tickets](https://support.inwink.com/tickets)
- - [English](https://help.inwink.com/pr%C3%A9parer-son-app-mobile)
    - [Français](https://help.inwink.com/fr/préparer-son-app-mobile)

  English
  
  Show submenu for translations
- [More support](https://help.inwink.com/kb-tickets/new)

 Hello ! How can we help you?

- There are no suggestions because the search field is empty.

1. [Help center](https://help.inwink.com/?hsLang=en)
2. [Mobile application](https://help.inwink.com/mobile-application?hsLang=en)
3. [Application configuration](https://help.inwink.com/mobile-application?hsLang=en#application-configuration)

# Prepare your mobile app

## Prepare your first mobile app step by step, from configuration through publication on the App Store and Google Play.

This help article guides you through the different steps required to prepare and launch your **first mobile app with inwink**, from defining its structure to publishing it on the app stores.

Before you begin, you will need to determine the type of app you need, configure the required access permissions, and prepare the different elements requested by Apple and Google.

### **Before you begin — Define your app type**

Before starting your project, begin by determining the structure of your app.

inwink supports three types of apps:

- **Event app**: for a specific event or edition, for example a conference or festival held every year.
- **Community app**: to provide permanent content to a community, such as articles, podcasts or videos.
- **Multi-event app**: to bring together several events or several editions within the same app.

**Good to know:** this choice determines the structure of your back office and how future app updates will be managed.

For example, with an event app, a new edition may require replacing the associated event. With a multi-event app, you can add new events to the existing app.

Once you have selected your app type, go to **Website and App \> Mobile App \> Publication** and complete the information required in the different steps.

---

### **Overview: the 7 steps**

**![Image ChatGPT 25 sept. 2026, 16\_24\_27](https://help.inwink.com/hs-fs/hubfs/Support/Agathe%20-%20Images%20AEL/Image%20ChatGPT%2025%20sept.%202026%2c%2016_24_27.png?width=670&height=377&name=Image%20ChatGPT%2025%20sept.%202026%2c%2016_24_27.png)**

---

### **Step 1 — Define your project**

The first step is to provide the main information required to create your app.

You will need to specify:

- the **app type** selected: event, community or multi-event;
- the associated event or community;
- the **app name**;
- its logo;
- the initial information and descriptions required to create it.

Select **New app**, then complete the form with the requested information.

---

### **Step 2 — Give access to your back office**

The inwink team must be able to access the relevant back office in order to configure and manage your app.

This access allows the team to:

- update certain content;
- configure the visual identity;
- prepare and publish app updates.

From your audience:

1. Go to **Permissions \> Access rights**.
2. Add the email addresses that were provided to you.
3. Assign them the **Webmaster** role.
4. If this role does not exist in your account, use the **Contributor** role, which provides equivalent permissions for this purpose.

Once this step is complete, the inwink team will have the necessary access to your back office.

---

### **Step 3 — Configure your Google Play Console account**

To publish your app on Android, you must have a **Google Play Console developer account**.

You will also need to grant the required access to inwink and Codemagic, the tool used by inwink to build and publish the app.

#### **Before you begin**

Prepare:

- your company’s **legal information**;
- a **bank card** to pay the Google Play registration fee ($25, one-time fee);
- your **privacy policy** (as a link or text).

#### **1. Create your Google Play Console account**

Create your Google Play developer account using your company information. You will receive an App ID that you will use in the form.

👉 Official Google tutorial:  
[https://support.google.com/googleplay/android-developer/answer/6112435?hl=en](https://support.google.com/googleplay/android-developer/answer/6112435?hl=en)

#### **2. Give inwink access**

From Google Play Console:

1. Go to **Settings \> Access control**.
2. Invite the inwink email address that was provided to you.
3. Assign the **Administrator** role.

#### **3. Give Codemagic access**

From the same **Access control** area:

1. Invite the Codemagic email address that was provided to you.
2. Assign the permissions required to manage app releases, specifically the **Release Manager** role.

Codemagic will build and publish your app.

#### **4. Add your privacy policy**

Enter the URL or content of your privacy policy in the requested fields. Google Play requires this information for compliance purposes.

#### **5. Add beta testers — Optional**

If you would like users to test your app before publication, provide the relevant email addresses.

**Important:** use the email address associated with the **Google account used on their smartphone**, which may not necessarily be their professional email address.

At the end of this step, your app is registered with Google Play and the required access permissions have been configured for both inwink and Codemagic.

---

### **Step 4 — Configure your Apple Developer account**

To publish your app on iOS, you must have an **Apple Developer account** and configure the required access and certificates so that inwink can manage your app.

#### **Before you begin**

Prepare:

- your **D-U-N-S Number** (obtaining one may take several days);
- your company’s legal information;
- a bank card to pay the fees ($99/year).

#### **1. Create your Apple Developer account**

Create your Apple Developer account as an organization using your D-U-N-S Number.

Apple may send you several verification emails during this process. Make sure you check them and follow the requested steps.

Official Apple tutorial:  
[https://developer.apple.com/help/account/membership/program-enrollment/](https://developer.apple.com/help/account/membership/program-enrollment/)

#### **2. Add a device for testing**

If necessary, register the iPhone or iPad that will be used to test the app in **App Store Connect \> Certificates, Identifiers & Profiles \> Devices**.

#### **3. Provide your Team ID**

Copy your **Team ID** (9 characters) from **App Store Connect \> Settings \> Team** and provide it in the form.

#### **4. Give inwink access**

From **App Store Connect \> Users and Access**:

1. Invite the inwink email address that was provided to you.
2. Assign the **Administrator** role.

#### **5. Generate the required keys**

inwink requires two keys (`.p8` files).

Two keys may be required for the app to operate and be published:

- an **APNs key**, mainly used for push notifications;
- an **App Store Connect API key**, used to publish the app.

These keys must be generated from your Apple environment under **Certificates, Identifiers & Profiles \> Keys**, then sent to inwink.

#### **6. Add beta testers — Optional**

You can also provide the email addresses of the users who will test the app via TestFlight.

**Important:** use the email address associated with the **Apple account used on their device**.

Once this step is complete, your Apple Developer account is configured and the inwink team has the required access permissions.

---

### **Step 5 — Configure push notifications with Firebase**

Push notifications allow you to send messages directly to app users.

For example, you can:

- announce that a new session has been added;
- remind users that a session is about to start;
- share important information during your event.

To manage these notifications on Android and iOS, the app uses **Firebase**.

#### **1. Create a Firebase project**

Create a dedicated Firebase project for your app at [https://firebase.google.com](https://firebase.google.com) to manage notifications.

#### **2. Give inwink access**

From your Firebase project settings:

1. Go to the section dedicated to **service accounts**.
2. Generate the requested private key (`.json`).
3. Send the file to your inwink contact.

#### **3. Create the Android app**

In your Firebase project under **Your apps**, create an Android app using your Android package name, for example:

`com.inwink.vivatechtalk2025`

#### **4. Create the iOS app**

Under **Your apps**, also add your iOS app using its **iOS Bundle ID**.

#### **5. Configure iOS notifications**

In **Firebase \> Project settings**, upload the APNs key (`.p8` file) generated in Step 4 and provide your Team ID.

Once this configuration is complete, inwink can manage push notifications on both Android and iOS.

---

### **Step 6 — Prepare the graphic assets**

Graphic assets are the different visual elements required for your app, for example:

- the app icon;
- the splash screen;
- logos;
- other images used in the app or on the app stores.

These files must meet the required dimensions and formats.

Download this guide to see where each element is displayed and the exact dimensions required:

**Graphic Assets Guide – Mobile App (PDF)**

**Important:** make sure you prepare the files according to the specifications provided to you to avoid rejection or integration issues.

Once your assets are ready, add them to the dedicated form.

Your app will then have all of its main graphic elements.

---

### **Your test version is ready**

Once the previous steps are complete, inform your inwink contact.

The inwink team will then be able to prepare your app and make it available as a **test version**.

You will be able to:

- install and test the app using a QR code or link;
- start configuring your content, such as events, pages and sessions;
- check your pages, events and sessions;
- adjust your visual identity, including colors, fonts and logos;
- review how the app looks before publication.

Before going live, you will still need to prepare the information that will appear on the app stores.

---

### **Step 7 — Prepare the App Store and Google Play listings**

The final step is to prepare the public information that will appear on your app listing in the App Store and Google Play.

You will need to complete:

- the app descriptions;
- the required keywords;
- screenshots;
- any other metadata required for publication.

Each field in the form specifies the information required and, where applicable, the character limits that must be respected.

As this content will be publicly visible, make sure you use clear wording that accurately represents your app.

Once the listings are complete, your app can be prepared for publication.

The inwink team then requests the production build and submits it to the app stores.

**Keep in mind:** approval by Apple and Google may take several days **(up to 2 weeks)**. Make sure you plan this step well in advance of your app’s planned launch date.

### **Key takeaways**

To prepare your first mobile app with inwink:

- first choose the app type that best fits your project;
- provide the information required to create it;
- give inwink the required access to your back office;
- configure your Google Play and Apple Developer accounts;
- prepare Firebase for push notifications;
- provide the app’s graphic assets;
- test your app before it goes live;
- finally, complete the App Store and Google Play listings.

Once all of these steps have been completed, your app can be submitted to the app stores for review and publication.

 

- [Essentials](https://help.inwink.com/essentials?hsLang=en#main-content)

    - [Grids](https://help.inwink.com/essentials?hsLang=en#grids)
    - [The fields](https://help.inwink.com/essentials?hsLang=en#the-fields)
    - [Publish](https://help.inwink.com/essentials?hsLang=en#publish)
- [Data](https://help.inwink.com/data?hsLang=en#main-content)

    - [Audience](https://help.inwink.com/data?hsLang=en#audience)
- [Events](https://help.inwink.com/events?hsLang=en#main-content)

    - [My event](https://help.inwink.com/events?hsLang=en#my-event)
    - [Participants](https://help.inwink.com/events?hsLang=en#participants)
    - [Program](https://help.inwink.com/events?hsLang=en#program)
    - [Speaker workspace](https://help.inwink.com/events?hsLang=en#speaker-workspace)
    - [Partners](https://help.inwink.com/events?hsLang=en#partners)
    - [Business Meetings](https://help.inwink.com/events?hsLang=en#business-meetings)
    - [Networking](https://help.inwink.com/events?hsLang=en#networking)
    - [Ticketing](https://help.inwink.com/events?hsLang=en#ticketing)
    - [Participant badge](https://help.inwink.com/events?hsLang=en#participant-badge)
    - [inwink onsite](https://help.inwink.com/events?hsLang=en#inwink-onsite)
    - [Online events](https://help.inwink.com/events?hsLang=en#online-events)
    - [Video integration](https://help.inwink.com/events?hsLang=en#video-integration)
    - [Online sessions](https://help.inwink.com/events?hsLang=en#online-sessions)
    - [Interactions](https://help.inwink.com/events?hsLang=en#interactions)
    - [Interactivity](https://help.inwink.com/events?hsLang=en#interactivity)
    - [Call for Papers](https://help.inwink.com/events?hsLang=en#call-for-papers)
    - [Commercialisation](https://help.inwink.com/events?hsLang=en#commercialisation)
- [Community](https://help.inwink.com/community?hsLang=en#main-content)

    - [Content](https://help.inwink.com/community?hsLang=en#content)
    - [Forums](https://help.inwink.com/community?hsLang=en#forums)
    - [Partner workspace](https://help.inwink.com/community?hsLang=en#partner-workspace)
    - [Configuration](https://help.inwink.com/community?hsLang=en#configuration)
    - [Groups](https://help.inwink.com/community?hsLang=en#groups)
    - [Memberships](https://help.inwink.com/community?hsLang=en#memberships)
    - [Ticketing](https://help.inwink.com/community?hsLang=en#ticketing)
- [Dashboards](https://help.inwink.com/dashboards?hsLang=en)
- [Emailings](https://help.inwink.com/emailings?hsLang=en#main-content)

    - [Send emails](https://help.inwink.com/emailings?hsLang=en#send-emails)
    - [Scheduled emails](https://help.inwink.com/emailings?hsLang=en#scheduled-emails)
- [Website](https://help.inwink.com/website?hsLang=en#main-content)

    - [Participant space](https://help.inwink.com/website?hsLang=en#participant-space)
    - [CMS](https://help.inwink.com/website?hsLang=en#cms)
    - [Webmaster](https://help.inwink.com/website?hsLang=en#webmaster)
    - [Languages and translations](https://help.inwink.com/website?hsLang=en#languages-and-translations)
    - [Partner space](https://help.inwink.com/website?hsLang=en#partner-space)
    - [Visual identity](https://help.inwink.com/website?hsLang=en#visual-identity)
    - [Blocks](https://help.inwink.com/website?hsLang=en#blocks)
    - [Registration forms](https://help.inwink.com/website?hsLang=en#registration-forms)
- [Connectors](https://help.inwink.com/connectors?hsLang=en#main-content)

    - [Paypal](https://help.inwink.com/connectors?hsLang=en#paypal)
    - [Six Payment](https://help.inwink.com/connectors?hsLang=en#six-payment)
    - [Power BI](https://help.inwink.com/connectors?hsLang=en#power-bi)
    - [Adyen](https://help.inwink.com/connectors?hsLang=en#adyen)
    - [Salesforce](https://help.inwink.com/connectors?hsLang=en#salesforce)
    - [Hubspot](https://help.inwink.com/connectors?hsLang=en#hubspot)
    - [Ingenico](https://help.inwink.com/connectors?hsLang=en#ingenico)
    - [Zapier](https://help.inwink.com/connectors?hsLang=en#zapier)
    - [Stripe](https://help.inwink.com/connectors?hsLang=en#stripe)
    - [Marketo](https://help.inwink.com/connectors?hsLang=en#marketo)
    - [Monetico](https://help.inwink.com/connectors?hsLang=en#monetico)
    - [Make](https://help.inwink.com/connectors?hsLang=en#make)
- [Mobile application](https://help.inwink.com/mobile-application?hsLang=en#main-content)

    - [Application configuration](https://help.inwink.com/mobile-application?hsLang=en#application-configuration)

[![inwink](https://help.inwink.com/hs-fs/hubfs/LOGO_RGB@600x-1.png?width=99&height=24&name=LOGO_RGB@600x-1.png "inwink")](https://www.inwink.com/)

<https://twitter.com/inwink_fr?lang=fr> <https://www.linkedin.com/company/inwink/mycompany/>

Copyright © 2025, inwink

```json
{
  "@context" : "https://schema.org",
  "@type" : "Organization",
  "address" : {
    "@type" : "PostalAddress",
    "addressLocality" : "Paris, France",
    "postalCode" : "75011",
    "streetAddress" : "33 Rue du Faubourg Saint-Antoine"
  },
  "email" : "contact@inwink.com",
  "funder" : [ {
    "@type" : "Organization",
    "name" : "Infinite Square",
    "url" : "https://www.infinitesquare.com/"
  } ],
  "logo" : "https://www.inwink.com/hs-fs/hubfs/inwink-H-rgb-1.png?width=140&name=inwink-H-rgb-1.png",
  "name" : "inwink",
  "owns" : [ {
    "@type" : "Product",
    "name" : "inwink",
    "url" : "https://www.inwink.com/"
  } ],
  "sameAs" : [ "https://www.linkedin.com/company/inwink/", "https://twitter.com/inwink_fr", "https://www.facebook.com/inwink-177090639388227/", "https://www.youtube.com/channel/UCWHQtvE5NEL7ijTKl4pGp0A" ],
  "url" : "https://www.inwink.com/"
}
```