
App Onboarding
Part of In-app messaging
Showing a message at the moment it helps
Choose in-app message timing from the user's task, a meaningful trigger and a current eligibility check.
Show an in-app message when it fits the task someone is doing. Define that moment by an observable app state and action, then confirm the message is still relevant. Time since installation or a screen count alone does not show a need for help.
Identify the useful moment
Start with the difficulty the message addresses: an unfamiliar control, a failed action, or returning to unfinished work. Identify what the app can observe. A pause alone does not prove confusion; the person may be reading or taking a break.
A useful rule might be: show the hint once when someone opens the relevant screen, the task is incomplete, the control is available and no sensitive flow is active. Before using a message, consider whether a persistent label would solve the problem more simply.
Moment / Question to ask
- First app open
- Is there a task on screen that needs this information?
- Failed action
- Does the message explain the failure and a next step?
- Return to unfinished work
- Is the task still open and its destination valid?
- Payment step
- Would the prompt interrupt a decision already under way?
When to show vs. when not to show a help message
- Show message whenThe user returns to an unfinished task, the control is available, and no sensitive flow is active.
- Do not show message whenThe user has just installed the app and hasn’t engaged with the relevant screen yet.
- Best alternativeUse a persistent label instead of a message if the information is always needed.
Trigger from a meaningful event
Choose an observable app event that marks the relevant step, then check task state before displaying a message. Firebase In-App Messaging ties messages to Google Analytics events, and Firebase's SDK documentation says additional integration can trigger message events outside the Analytics framework.
Google Analytics collects some app events automatically. screen_view fires when a screen transition occurs and the new screen name differs from the previous one; first_open marks the first launch after installing or reinstalling; app_exception records when the app crashes or throws an exception, once Firebase Crashlytics is integrated. A custom event for the exact task step is usually more precise than any of these.
In Braze, in-app messages are triggered when the SDK logs Session Start, Push Click, Any Purchase, Specific Purchase or a Custom Event. They can't be triggered through the API or by API events, only by custom events logged by the SDK, so the moment must exist as an event inside the app.
A worked rule: log a custom event when saving a draft fails, trigger the help message on that event, and before display confirm that the draft is still unsaved and no payment screen is open. Stop the message once a later save succeeds.
Plan how the app will check task state before displaying a message. A trigger alone does not establish that the message is relevant to the app's current state.
If a temporary app flow makes the message inappropriate, defer display until that flow has ended. Firebase's Android SDK lets the app check whether messages are suppressed with areMessagesSuppressed(). Treat this as a current-state check, not as a substitute for checking whether the message is still relevant.
Define when the moment ends
A draft reminder should stop when the draft is submitted or discarded. Help for a new control may stop after successful use, dismissal or a later product change, depending on the message's purpose. Reopening the app should not by itself make an obsolete prompt relevant again.
Space messages out. By default the Braze SDK rate-limits triggered in-app messages to once every 30 seconds, and Braze advises production apps not to set this value lower than 10 seconds, so users aren't overwhelmed with back-to-back in-app messages.
Check the planned rule with the app already open, after backgrounding, after quick task completion and after a restart. Compare what should appear with what actually appears on supported devices.
Judge timing by task continuation and completion, as well as dismissal and exit. Firebase's Android SDK can register click, dismiss and impression listeners for these signals. A high tap rate can coexist with poor timing if the message draws people away from the task it was meant to help.
Further reading: Modify behavior of Firebase In-App Messaging messages (firebase.google.com).



