What is in-app messaging?
In-app messaging is communication shown inside a web or mobile product while someone is using it, such as banners, modals, slideouts and small nudges. It reaches active users in the context of what they are doing, unlike email or push notifications, which reach them outside the product.
In-app messaging vs push notifications: what's the difference?
The difference is where the user is when the message lands. In-app messages appear while the user is already in the product. Push notifications appear on the device's lock screen or notification tray when the user is somewhere else.
| In-app messaging | Push notifications | |
|---|---|---|
| Reaches | Users who are active right now | Users who are away from the product |
| Job | Help with what they're doing in this session | Bring them back for a reason |
| Permission | None needed beyond being signed in | The user has to opt in |
| Context | Can target the exact screen and state | Knows only what you stored about the user |
| Good for | A new feature next to where it lives, a plan limit, a setup step | A teammate's comment, a finished export, a reminder |
They work best as a pair. A push notification says "your report is ready"; once the user taps through, an in-app message can point to the new filter on that report. Using push for something that only matters inside the product, or in-app for something time-sensitive while the user is away, is a common mismatch.
What types of in-app messages are there?
In-app messaging has a second meaning: chat inside an app, between users or between a user and a support team. This page covers the messages a product sends to its users.
- Banners. A strip at the top or bottom of the screen for account-wide news: a billing issue, planned downtime, a renewal date.
- Modals. A centered window that blocks the screen until it's closed. Reserve it for things the user must see before continuing.
- Slideouts. A smaller panel from the corner that doesn't block work. Good for announcements and optional offers.
- Nudges and hotspots. A small pulse or label on one element, often paired with tooltips, to point at a feature.
- Inbox or announcement feed. A list the user opens when they choose to, so news doesn't interrupt.
Targeting is what separates useful messages from noise. The best in-app messaging triggers on behavior (the user just created their third project), on account state (the plan is near its seat limit) or on page (they're on the reports screen), and caps how often any one person sees a message.
When does in-app messaging help, and when do users want the task done?
In-app messaging helps when the user needs to know something: a change, a limit, an option they haven't found. It is weaker when the user is trying to do something and the message can only describe the steps.
Picture a project-management tool. A new admin sees a slideout saying "Invite your team to get started," then a nudge on the Members button, then a modal explaining roles. Each message is accurate. But the admin wanted the team invited, and the messages handed the work back to them three times.
A useful test: if the message ends with "click here, then here, then here," the user probably wanted the task done, not described. That's where an agent that does the step with the user fits better than another message.
Foldspace takes that approach: users ask for the outcome, such as "invite my team from this spreadsheet as editors," and the Product Agent does it in the product, as that user and with that user's permissions.