Mobile App FAQ

Q: What is the difference between channel settings, screens, and widgets?

A: Difference between these types:

• SETTINGS controls channel-wide behavior and visual defaults.
• SCREENS controls the major app screens and their publication status.
• Widgets are ordered content blocks used to build configurable screens such as Homepage and Profile.

Q: Does saving a screen as a draft publish it?

A: No. Save as Draft stores the draft configuration. Return to the screen list and confirm that the required screen shows PUBLISHED before launch.

Why can the physical app look different from the editor preview?

The preview is a configuration aid. A physical device also uses real member data, login state, segment membership, device dimensions, operating-system behavior, and the published configuration. Always complete device testing before launch.

Q: What is the difference between Initial Language and Available Languages?

A: Initial Language is the default app language. Available Languages defines the languages that a customer can use.

Q: Can I change translation placeholders?

A: Do not change dynamic placeholders for timestamps, amounts, currencies, counts, or other inserted values. Translate only the surrounding customer-facing text unless the implementation owner confirms a different placeholder format.

Q: How is the bottom-navigation order defined?

The order of values in SETTINGS → GENERAL → Menu Routes determines the bottom-navigation order.

Q: Can a bottom-navigation item open a website?

A: Yes. Use embed:menu_link in Menu Routes and store the URL in Menu Link (common.menu_link) under TRANSLATION.

Q: Can I use any value in Menu Routes?

A: No. Use only route values supported by the project. Test every route after changing the array.

Q: What is the difference between App Welcome and Onboarding?

A: App Welcome is shown once after a fresh installation. Onboarding is shown after the customer's first login or registration.

Q: Which screen types can App Welcome contain?

A: The demonstrated editor supports:

• Welcome screen
• Language screen
• Info screen

Q: Which screen types can Onboarding contain?

A: The demonstrated editor supports:

• Welcome screen
• Info screen
• Card screen
• Preference center screen

The Card screen supports the project's flow for pairing an existing loyalty card or generating a new one.

Q: Can App Welcome or Onboarding contain multiple steps?

A: Yes. Click Add new, configure each item, and drag the items into the required order.

Q: Why does App Welcome not appear again during testing?

A: App Welcome is designed to appear once after a fresh installation. Retest it in a clean-install state.

Q: Why does Onboarding not appear for an existing member?

A: Onboarding is associated with the first login or registration journey. A member who already completed that journey may not see it again. Test with the appropriate first-login or first-registration state.

Q: How do I add a widget?

A: Open a widget-based screen such as Homepage or Profile, click Add new, select the Widget type, and configure its common and type-specific settings.

Q: Where is a new Homepage widget added?

A: A new widget is added to the end of the widget list and initially uses the Static type as a default.

Q: How do I change the order of widgets?

A: Drag widgets using the reorder handle. The app displays them in the order shown in the editor.

Q: Can I prepare a widget without showing it?

A: Yes. Set Visibility to None and save the widget. Change the visibility only when the widget is ready.

Q: What happens when no segment is selected?

A: The widget is not restricted by segment. Its Visibility rule still applies.

Q: Can an embedded browser close after a completed external flow?

A: Use Close Browser on specific URL and enter the completion or callback URL used by the flow. Test the complete redirect sequence on physical devices.

Q: Can screenshots be blocked for an embedded web page?

A: The web-link configuration includes Block screenshot for supported embedded flows. Screenshot behavior must be tested on each supported device platform.

Q: How do I display the same header on every screen?

A: Configure SETTINGS → HEADER WIDGETS → Widget for header. The shared header is used on each Mobile App screen unless it is overridden.

Q: How do I display a header on only one screen?

A: Leave the global header empty and add a Header widget to the required screen.

Q: Can the header contain a personalized greeting?

The Header widget supports a greeting and can display personalized member information supported by the project's template configuration. Confirm the exact template syntax used by the project before publication.

Q: Why is Contest notification empty or hidden?

A: The Contest notification widget is displayed when the member has an unused contest token. Test it with a member who is in that state.

Q: Can a widget use an image or video?

A: Supported upload fields can accept images and, for some fields, MP4 video. Use the file formats, maximum size, and recommended dimensions displayed by the specific upload control.

Q: Which dimensions should I use for a Static widget image?

A: Select the widget height first. The editor displays the recommended dimensions for the active Tiny, Small, Medium, or Large configuration. Follow the dimensions sh

Q: What happens when the customer does not allow GPS access?

A: If the app uses a map, Mapbox Position provides the default map position when the current device position is unavailable or permission has not been granted.

Q: Can screenshots of card and coupon barcodes be blocked?

A: Use SETTINGS → SCREENSHOT BLOCKER:

• Block on Loyalty Card Detail protects the loyalty-card barcode or QR code.
• Block on Coupon Detail protects coupon detail when a barcode or QR code is visible.

Test the behavior on every supported platform.

Troubleshooting

Widget Sizes