--- title: Mobile app content description: Learn how to configure your inwink mobile app content, customize pages and menus, manage navigation, preview your changes and publish them. --- [Skip to content](https://help.inwink.com/contenu-app-mobile#main-content) - [English](https://help.inwink.com/contenu-app-mobile) - [Français](https://help.inwink.com/fr/contenu-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/contenu-app-mobile) - [Français](https://help.inwink.com/fr/contenu-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) # Mobile app content ## Configure the pages, menus and navigation of your inwink mobile app, then test and publish your changes.Créer, organiser et personnaliser les pages de votre application mobile. ### **1. Access the app content** From the **Website & App \> Mobile app \> App content** menu. The screen is divided into two areas: - **Navigation**: the app navigation entries — header, main menu and burger menu. - **Pages**: all the pages available in the app. --- ### **2. Page types** In the mobile app CMS, each content block is called a **page**. Some pages are available by default in the view: you do not need to create them, you simply make them available by clicking **Customize**. Other pages can be added using the **Add a page** button. The available pages depend on the context of your project: event or community. They are divided into two categories: navigation pages, which determine how participants move through the app, and content pages, which display information. #### **2.1 Navigation pages** Three pages can be used to organize navigation within the app. None of them are enabled by default: you can use one, two or all three, depending on how you want to structure the navigation.  ![Image ChatGPT 25 sept. 2026, 17\_40\_05](https://help.inwink.com/hs-fs/hubfs/Support/Agathe%20-%20Images%20AEL/Image%20ChatGPT%2025%20sept.%202026%2c%2017_40_05.png?width=488&height=534&name=Image%20ChatGPT%2025%20sept.%202026%2c%2017_40_05.png) - **The header** is displayed at the top of the app home page. It can contain a title, an image, or both. - **The burger menu** opens from the left side of the screen when the participant taps the icon in the top-left corner. It displays pages as a vertical list. This is the recommended location for secondary pages — FAQ, practical information, site map — or when there are too many pages to fit in the main menu. It also manages login and app registration options. - **The main menu** is displayed at the bottom of the screen and remains visible at all times. Each page is represented by an icon and a short label. It is designed for the most frequently accessed pages, which participants should be able to reach in a single tap: Home, Agenda, Networking, Participant badge, Partners. #### **2.2 Content pages** **1. Structural page:**A structural page brings several types of content together in a single view. It serves as the entry point to a major section of the app. It comes with a ready-to-use layout that you can keep as is or customize to suit your needs. **Event context:** Home, Event agenda, Networking Hub, Partner Hub. **Community context:** Home, News feed, People Hub, Content Hub, Group home. **2. List page:** A list page displays all items belonging to the same content type. Two of these pages display items in a calendar rather than a list: Sessions and Business meetings. **Event context:** Themes, Tracks, Partners, Partner offers, Onsite services, Rooms, Sessions, Sessions (calendar), Speakers, Abstracts, Business meetings (calendar). **Community context:** Articles, Videos, Documents, Podcasts, Events, Interests, Partners, Partner offers, Members, Contacts, Groups, Forums, Other communities. **3. Detail page:** A detail page displays the information for a specific item: this is the page participants open when they select an item from a list. Each content type has its own detail page, named after the corresponding content. For sessions, for example, you will find a **Sessions: list** page and a **Session: details** page. **Event context:** Theme, Track, Partner, Partner offer, Onsite service, Room, Session, Speaker, Abstract, FAQ category, FAQ section, Contact details. **Community context:** Article, Video, Document, Podcast, Event, Interest, Partner, Partner offer, Member, Group, Forum, Community, FAQ category, FAQ section. **4. Feature page:** These pages do not display content that you enter manually. Instead, they enable a feature within the app. Their content depends on the configuration of the corresponding feature elsewhere in the back office. **Event context:** Map, Registration, Contact search, Global search, Leadgen, AI Navigator. **Community context:** Registration, Search, AI Navigator. **5. Participant space page:** These pages display information specific to each logged-in participant: their profile, contacts and saved content. Their content is generated from the participant’s activity, so you do not need to populate it manually. **Event context:** Profile, Badge, Favorites, Favorite partners, Agenda, Contact requests, Contact recommendations, My contacts, Conversation list. **Community context:** Profile, Favorites, Discussions. --- ### **3. Enable and customize a page** Setting up your content involves three steps: first, make the page you need available, then configure its content, and finally add it to the menu of your choice. #### **3.1 Make a page available** There are two methods, depending on the page you are looking for. **For a page available by default in the view:** 1. Find the page you want in the list. 2. Click **+ Personalize**. ![](https://help.inwink.com/hs-fs/hubfs/image-png-Sep-25-2026-03-43-41-0029-PM.png?width=670&height=32&name=image-png-Sep-25-2026-03-43-41-0029-PM.png) **For other pages:** 1. Click **Add a page**. 2. Select the type of page you want to create from the available templates. In both cases, the page then appears in the list and can be configured. You can keep it as is or modify its content. A page cannot be added to a menu until it has been made available. #### **3.2 Edit the content of a page** Click the pencil icon for the relevant page. A preview on the right-hand side of the screen allows you to see how the page will appear in the app as you make changes. The configuration is divided into several tabs: - **Content** — the page title, which you can edit, and the blocks that make up the page: text, image, search, session list, button, etc. You can freely add and remove blocks. - **Display** — the page layout: block order, column or list display. - **Data** *(list pages only)* — filters applied to the displayed data and sorting options: chronological order, alphabetical order, etc. - **Filters** *(list pages only)* — the search fields available to participants (title, description, image, tags) and the available filters. - **Conditions** — page visibility rules, based on the participant’s status or the value of a field. - **Onboardings** — displays an onboarding when the page is opened for the first time. ### Customize a block Each block can be edited using its pencil icon and moved to change its display order. The available options depend on the type of block: a *Program* block offers filters for sessions, while an *Image* block lets you add a visual and a clickable link. #### **3.3 Add a page to a menu ![](https://help.inwink.com/hs-fs/hubfs/image-png-Sep-25-2026-03-44-50-7244-PM.png?width=832&height=764&name=image-png-Sep-25-2026-03-44-50-7244-PM.png)** 1. Click the navigation page you want to configure: header, burger menu or main menu. 2. Under **Menu items**, click **+ Add**. 3. Enter the **Label**: the name that will appear in the menu. 4. Select an **Icon before**. 5. Under **Link**, select *App page*, then choose the page to display. 6. Click **Apply**. This validates the menu item entry. The menu configuration itself still needs to be saved — see *Save the configuration*. ![](https://help.inwink.com/hs-fs/hubfs/image-png-Sep-25-2026-03-45-11-5817-PM.png?width=832&height=424&name=image-png-Sep-25-2026-03-45-11-5817-PM.png) Each menu item displays two lines: the label you entered and, underneath, the name of the page it links to. These two names may be different — in the example above, the “Program” menu item links to the “Sessions: list” page. #### **3.4 Highlight a menu item** The **Highlight** option, available in the *Action* tab, visually distinguishes an item from the others in the menu. Its icon is then displayed inside a circle and its label no longer appears below the icon. The item can be placed anywhere: its position depends solely on its location in the list of menu items. However, placing it in the center can give it greater visual impact.   ![](https://help.inwink.com/hs-fs/hubfs/05-mettre-en-avant-png.png?width=304&height=88&name=05-mettre-en-avant-png.png)  #### **3.5 Edit, reorganize or delete a menu item** Each item in the list has three actions on the right: - The pencil icon opens the configuration window so you can edit the item. - The trash icon removes it from the menu. - The icon on the left of the item allows you to move it by dragging and dropping. The order in the list corresponds to the order in which items appear in the app. The **Hide navigation bar** toggle at the top of the screen disables the entire menu without deleting the items it contains. #### **3.6 Define display conditions** You can restrict an item’s visibility to certain participants. In the item configuration window, open the **Display conditions** tab. ![](https://help.inwink.com/hs-fs/hubfs/image-png-Sep-25-2026-03-46-17-4830-PM.png?width=843&height=453&name=image-png-Sep-25-2026-03-46-17-4830-PM.png) - **Hide this menu** removes the item from view for all participants. - **Participant status** restricts the item to participants with the selected status. - **Display content if** conditions the display based on the status of a piece of content. - **URL parameter conditions** conditions the display based on parameters included in the access URL. Click **Apply** to confirm. #### **3.7 Save the configuration** Once all tabs have been configured, two buttons are available at the bottom of the screen: - **Apply** applies your configuration to the preview on the right-hand side of the screen and updates the mobile app in beta test mode. This allows you to check the actual result before confirming your changes. - **Save** saves the configuration and closes the window. These two actions are complementary: until you save, the applied configuration is not retained. If you leave the screen without saving, both the preview and beta test mode revert to the last saved configuration. #### **3.8 Publish pages** Saving and publishing take place at two different levels. **Apply** and **Save** validate a page’s configuration, while publishing is managed from the page overview. As soon as you save a page, its configuration becomes available in preview: the **Preview** label appears on the page. It is not yet visible in production. To make it available in production, publish it. After a page has been published for the first time, it displays both labels: **Preview** and **Published**. There are two ways to publish: - From an individual page, to publish only that page. - Using the **Publish all** button, to publish all modified pages at once. **Best practices** - Test your pages in preview before publishing. - Limit the number of items in the main menu to avoid overcrowding the navigation. - Place secondary information in the burger menu. - Use display conditions to tailor the app to each participant profile. - [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/) 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/" } ```