Table of contents
In-app messages are custom messages that appear while a mobile app is in the foreground. Unlike push notifications, they do not appear when the app is in the background or closed.
In-app messages can:
- Be created with raw HTML or a drag-and-drop editor.
- Contain buttons for closing the message or navigating to specific content.
- Be sent as part of blast, triggered, or workflow-based campaigns.
- Be displayed in any order, or prevented from displaying at all.
- Contain metadata that the associated mobile app can inspect.
- Point to new content or functionality in your app, promotions, and other important information.
How an app receives in-app messages
Iterable in-app works by sending a silent push to your app to notify the client side that there is an in-app message in the queue, ready for our user to view.
Example in-app workflow
- A marketer sets up an Iterable in-app or Mobile Inbox in the Iterable dashboard.
- The Iterable system sends a silent push notification to the mobile app.
- The mobile app receives the silent push and pulls down (does a GET request) the most recent in-app messages.
- Remote messages on the server are added to the local storage for increase performance and speed.
- The user is presented the in-app(s) messages with little workload on client-side performance.
A custom payload enbales developers to include:
- Prioritization around which in-app messages to show first
- Determine which view should present the in-app message
- Apply additional personalization with Handlebars