---
title: App mobile, ce qu'il faut savoir avant de se lancer
description: Understand how an inwink mobile app works, how it is published on the App Store and Google Play, and what to anticipate before launching it.
---

[Skip to content](https://help.inwink.com/app-mobile-ce-quil-faut-savoir-avant-de-se-lancer#main-content)

- [English](https://help.inwink.com/app-mobile-ce-quil-faut-savoir-avant-de-se-lancer)
- [Français](https://help.inwink.com/fr/app-mobile-ce-quil-faut-savoir-avant-de-se-lancer)

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/app-mobile-ce-quil-faut-savoir-avant-de-se-lancer)
    - [Français](https://help.inwink.com/fr/app-mobile-ce-quil-faut-savoir-avant-de-se-lancer)

  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)

# App mobile, ce qu'il faut savoir avant de se lancer

## Understand how a mobile app works, how it is published on app stores, and the differences between iOS, Android and the web.

Are you considering offering a mobile app for your event? Before getting started, it is important to understand how it works, how it differs from a website, and why certain validation steps are required before it can be published.

This guide covers the key concepts you need to know about iOS and Android mobile apps, their publication on app stores, and how they are updated.

### **Mobile app vs. website: what are the differences?**

A website and a mobile app do not work in the same way.

When you visit a website, content is loaded from the Internet each time you access it. If information is changed, such as a time or description, the new version becomes available as soon as you refresh the page.

A mobile app, on the other hand, is **installed directly on your smartphone or tablet**.

This allows it to:

- store certain information on your device
- provide an experience tailored to mobile use
- continue displaying certain content when the Internet connection is limited
- use smartphone-specific features such as push notifications.

This difference also explains why some changes **require an app update**, while others can be published directly from the inwink back office.

---

### **Understanding iOS and Android**

A mobile app must run on an **operating system**, also known as an OS.

An operating system is the main software that allows your smartphone to function and applications to run.

The two main mobile operating systems are:

- **iOS**, developed by Apple for iPhones and iPads
- **Android**, developed by Google and used by many smartphones, including Samsung and Google Pixel devices, as well as devices from other manufacturers.

These two environments work differently.

From a technical perspective, a version of the app is therefore required for each operating system.

**Key point:** with inwink, you manage your content from a single back office. The inwink team handles the iOS and Android versions as well as their technical maintenance.

You therefore do not need to manage your content twice.

---

### **Why does an app need to be approved by the app stores?**

Before a mobile app can be downloaded by your participants, it must be published on:

- the **App Store** for Apple devices
- the **Google Play Store** for Android devices.

Apple and Google review apps before making them available for download.

This review allows them to check, among other things:

- that the app works properly
- security
- the permissions requested by the app
- the content and information displayed on the app stores
- screenshots
- compliance with their publishing guidelines.

For example, the screenshots used to present your app must reflect the content **actually available to users**.

The app stores may also need to access protected features of your app during the review process. The information required for this testing is prepared with the inwink team.

---

### **How does the app publication process work?**

For a first publication, the process generally follows these steps:

1. You configure your content in your inwink back office.
2. The app is prepared for publication.
3. It is submitted to Apple and Google.
4. The app stores review the app.
5. The app is approved or changes are requested.
6. Once approved, it becomes available for download.

**Important:** approval depends directly on Apple and Google.  
The review time and any correction requests therefore cannot be fully controlled by inwink.

For this reason, we recommend starting the publication process **at least 3 months before the planned launch of the app**.

---

### **What happens if the app is rejected?**

If Apple or Google rejects an app, the reasons for the rejection are provided.

The inwink team can then:

- identify what needs to be corrected
- make the necessary changes
- resubmit the app.

A rejection does not mean that your app cannot be published, but it may extend the time required to launch it.

**Make sure you allow for this possibility in your schedule.**

---

### **iOS and Android: why should you test both versions?**

Even though content is managed from the same place in inwink, iOS and Android remain two different environments.

They may differ in terms of:

- screen sizes and formats
- certain interface behaviors
- operating system versions used by participants
- publishing guidelines
- certain platform-specific features.

It is therefore important to test the app on **both an iOS device and an Android device** before launch.

**Key point:** the fact that the app works correctly on an iPhone does not automatically guarantee identical behavior on Android, and vice versa.

Make sure you allow enough time to test both environments.

---

### **Does changing content require an app update?**

In most cases, **no**.

After the app has been published for the first time, changes made to your content from the inwink back office can be published without submitting a new version to the app stores.

This is particularly the case if you modify:

- a time
- a session
- an event
- a description
- a photo
- a speaker profile
- certain editorial information.

Once these changes are published from your back office, the app can retrieve the updated information.

You can therefore continue updating your content without triggering a new publication on the App Store or Google Play.

---

### **When does the app actually need to be updated?**

A new version of the app is generally required when a change directly affects its technical operation.

For example, this may apply to:

- adding a **new feature**
- fixing a **bug that requires a technical change**
- a major update to **graphic assets**
- a security update
- adapting the app to a new version of iOS or Android
- a major change to the app requiring a new submission.

In these cases, a new version must be prepared and, depending on the change, submitted to the app stores.

The key distinction to remember is:

**Content in the back office → generally no app update required**

**Technical change to the app → a new version may be required**

---

### **Can the app work with a poor Internet connection?**

The app is designed to store some of the information required for its use locally.

During use, certain event data may be saved on the device, for example:

- the agenda
- descriptions
- content-related information
- certain images.

The app can therefore continue displaying some of this information even when the connection is limited.

However, some features that require a real-time connection may still depend on Internet access.

---

### **How much time should you allow before launching the app?**

For a first app, several steps need to be anticipated:

- creating and validating the required accounts
- configuring the app
- testing on iOS and Android
- preparing the content
- submitting the app to the stores
- approval by Apple and Google
- any corrections requested after the first submission.

We therefore recommend starting the process **at least 3 months before the planned launch date of the app**.

This timeframe also allows enough time to carry out the necessary testing before making the app available to your participants.

---

### **Who manages what between inwink and you?**

You mainly manage the **content of your app from your inwink back office**.

You can manage, among other things, your event information, content, agenda and the elements visible to your participants.

The inwink team handles the technical aspects of the app, including:

- the iOS and Android versions
- technical maintenance
- submissions to the app stores
- any corrections related to app store rejections
- technical updates.

This gives you a single environment in which to manage your content, regardless of the device used by your participants.

### **Key takeaways**

Before launching your mobile app:

- understand the difference between how a mobile app and a website work
- keep in mind that there is a version for **iOS and Android**
- test your app on both operating systems
- anticipate the mandatory approval process by the App Store and Google Play
- allow at least **3 months before launch** for a first publication
- continue updating your content from inwink without systematically republishing the app
- request a technical update only when the app’s operation or structure changes.

This allows you to regularly update your content while keeping your app available and up to date for your participants.

 

- [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/"
}
```