Configure triggers and button actions on Edit Info Screen → Workflow. Export with on the screens list.
Screen types and trigger events
Catalogs for Info Screens configuration
Overview
An info screen is shown when all of these match: the app reaches a trigger event, optional Param text, the member’s platform, and a published screen in Active status. The screen type decides layout (modal vs full page vs carousel).
Screen types
Admin label → what members experience → when to choose it.
| Type (Admin label) | What members see | When to use | Editor notes |
|---|---|---|---|
| Popup | Centered modal over a dimmed background. | Short notices, confirmations, single-step prompts. | Draggable field order; default title 28 px. Opens as overlay dialog. |
| Curtain | Bottom sheet sliding up from the lower edge (bottom modal). | Longer copy that should not cover the entire screen; feels less interruptive than a center popup. | Same field list as popup; preview shows sheet layout. |
| Full Screen | Full-page layout with vertically stacked blocks. | Welcome flows, policy summaries, or any message that needs the whole screen. | Default title 36 px. Navigates to dynamic-screens route. |
| Slider Screen | Full-page horizontal swipe through text slides. | Multi-step onboarding tips without separate images per slide. | Body editor becomes a list of slide strings; field reorder disabled. |
| Cards Screen | Full-page list of expandable tiles—each row shows a title; tapping expands body text and an optional image (accordion style, not a horizontal carousel). | FAQ-style help, policy sections, or multi-topic explainers where members expand one topic at a time. | Cards editor—add/remove/reorder cards (title, body, image per card). Published JSON is read as expandable tiles in the member app. |
| Menu Screen | List of tappable rows, each with its own follow-up action. | Support hub, settings explainer, or “choose your path” menus. | Menu table with per-row next event; body area is the menu editor. |
| Tabs Screen | Inactive (July 2026) — not safe for production. | Grouped content where members switch tabs in one flow. | Admin has the type in the picker but no tab-list editor. The member app route exists with tab labels and bodies commented out and no tab data in published JSON—publishing this type today will not show your content. Use Menu Screen, Grid Screen, or separate screens until engineering wires tabs end-to-end. |
| Content Screen | Full-page layout using the standard dynamic content blocks (title, body, images, buttons) via the shared content renderer. | Single-topic full pages—about text, legal copy, or one story with primary/secondary actions. | Standard Edit screen field list (not the cards or grid editors). The app may inject build/version placeholders into button copy when configured. |
| Grid Screen | Full-page tile grid (two columns by default)—each tile shows title, optional subtitle, and icon or image; tapping runs the tile’s next action. | Support hub home, “choose a topic” dashboards, or shortcuts into App Content categories. | Grid editor table per tile: title, subtitle, icon/image, disabled flag, next event + action. Tiles can open a content category feed or chain to another screen/event. Column count and tile aspect ratio come from screen styles. |
| Instruction Screen | Bottom sheet with good/bad example images per step. | Photo quality, profile etiquette, or “do / don’t” visual guidance. | Dedicated instruction form with bad/good image uploads per step. |
Type-specific editors
Field-level reference for Grid Screen, Menu Screen, and Slider Screen on Edit Info Screen. Popup, Curtain, Full Screen, Content, Cards, and Instruction types use the standard draggable field list on the Edit tab.
Grid Screen editor
Shown when Type = Grid Screen. Layout controls sit above the tile table; expand a row (+) to set icon and navigation.
| Field | What to enter | Member effect |
|---|---|---|
| Grid columns | Number of columns (default 2). | Column count in the member app tile grid. |
| Tile aspect ratio | Decimal height÷width per tile (helper suggests desktop ~1.85; higher = shorter tiles). | Controls tile height in the grid layout. |
| Title / Subtitle (per row) | Short label and optional second line on the tile. | Visible on each grid cell before tap. |
| Disabled | When on, tile appears but cannot be tapped. | Grayed / non-interactive tile. |
| Icon / image (expanded row) | Upload one image per tile. | Tile artwork in the app grid. |
| Next event type + action target (expanded row) | Same action picker as workflow buttons — e.g. open another screen, app page, content category, comm trigger, or custom action. | Runs when the member taps the tile. Content category opens the app content feed for the category you pick. |
| Add grid item | Appends an empty row; drag handle reorders. | Order in the table = left-to-right, top-to-bottom order in the app. |
Menu Screen editor
Shown when Type = Menu Screen. Each row is one tappable menu line on the published screen.
| Field | What to enter | Member effect |
|---|---|---|
| Title / Subtitle | Primary and secondary line on the menu row. | Visible on the Me-page style menu list. |
| Highlighted (column or expanded checkbox) | When on, row uses emphasized border/icon styling. | Draws attention to one entry (e.g. premium upsell). |
| Tile icon (expanded row) | Optional uploaded icon. | Leading icon on the row. |
| Next event type + action target | Per-row navigation — independent for each menu item. | Member taps the row → app runs that action (open screen, settings route, content feed, etc.). |
| Add Tile | Appends a row; drag to reorder. | Row order = top-to-bottom order in the app. |
Slider Screen editor
Shown when Type = Slider Screen. The main Body area becomes a draggable list of text slides (field reorder on the standard Edit tab is disabled for this type).
| Field | What to enter | Member effect |
|---|---|---|
| Text (per slide) | Multiline copy for one horizontal page. | One swipe panel in the full-screen slider. |
| Drag handle | Reorder slides. | Swipe order left-to-right matches Admin order. |
| Remove (slide 2+) | Deletes that slide string. | Removes a panel from the carousel. |
| Add Text | Appends a blank slide. | Adds another swipe step. |
Pair slider screens with a workflow Next event on the primary button when members should continue after the last slide.
Cards Screen editor
Shown when Type = Cards Screen. The Edit tab body is replaced by a draggable card list (not the standard title/body field reorder).
| Field (per card) | What to enter | Member effect |
|---|---|---|
| Title | Row heading on the accordion tile. | Collapsed label before the member expands the topic. |
| Body | Multiline text (about four lines in the editor). | Expanded content under the title. |
| Image | Optional upload per card. | Illustration shown inside the expanded tile. |
| Remove Card | Deletes the card (available on every card after the first). | Removes that FAQ section from the member list. |
| Drag handle | Reorder cards in the list. | Vertical order in the app accordion. |
| Add Card | Appends an empty title/body/image card. | Adds another expandable row. |
Cards do not have per-row next events — use screen-level workflow buttons for navigation after the member reads the FAQ list.
Choosing Popup vs Curtain vs Full Screen
Use this when the Type dropdown on a new screen is not obvious. All three can show title, body, and buttons—the difference is how much of the app the member still sees underneath.
| If you need… | Pick this type | Why |
|---|---|---|
| A short yes/no or single action while the member stays on the same page | Popup | Center modal; member sees dimmed content behind it; dismiss returns to the same place. |
| More text or a small form without taking the whole screen | Curtain | Bottom sheet; feels lighter than a center popup; good for explanations with one primary button. |
| Policy text, welcome story, or anything that should feel like a dedicated page | Full Screen | Replaces the current view until the member taps through or closes; use when context behind the message would distract. |
| Multiple swipeable tips with no images | Slider Screen | Horizontal text slides on a full page—not a modal. |
| FAQ-style sections the member expands one at a time (title + body + optional image) | Cards Screen | Vertical accordion list—not a swipe carousel. |
| A dashboard of tappable tiles (icons or images) that open categories or other screens | Grid Screen | Best for “pick a topic” hubs; each tile has its own next action. |
| A list of choices, each opening another screen or action | Menu Screen | Rows with per-item Next event; not a single body block. |
| Step-by-step “good vs bad” photo examples | Instruction Screen | Bottom sheet with paired example images per step. |
Workflow reminder: Set Trigger event and Param on the Workflow tab, choose Active status, then from the screens list. Inactive or draft screens never appear in the member app bundle.
Trigger events
Set Trigger event on the workflow tab. Use Param when the same event needs multiple screens.
| Event (Admin label) | When the app tries to show a screen | Param usage | Verification |
|---|---|---|---|
| None | Never auto-triggered—use only when chaining from another screen’s next event. | — | verified |
| After approve | After a profile or introduction approval action completes. | Optional status-specific screens when the app passes a status param. | verified — public profile / approval flows |
| Profile open | When a member opens someone’s public profile. | Often the viewed profile’s status id. | verified |
| Add child | Parent-account flow when adding a child profile. | — | verified |
| Welcome | When a signed-out user hits a protected route—the app may show a welcome full-screen flow instead of login. | — | verified — app navigation guard |
| No suggestions | When the potential-matches list is empty. | — | verified |
| Payment successful | After a successful in-app payment. | Payment product or tier id when the app passes one. | verified |
| Extend suggestion | When a member uses “extend suggestion” on an introduction. | Introduction context param when provided. | verified |
| Settings | Opening the settings router from the app menu. | — | verified |
| Why we ask this | Member taps “why we ask” on a questionnaire question. | Question id when available so you can target one question. | verified |
| End onboarding | When onboarding chat marks the onboarding batch complete. | — | verified |
| Questionnaire end | When a questionnaire batch finishes (after-login or home Lora flows). | — | verified |
| System shutdown | When the brand is in maintenance / shutdown mode and the member opens matches. | — | verified |
| Pre login end | Intended for end of pre-login Lora experience. | — | Inactive (July 2026): Admin lists this trigger, but the member app never calls it when showing the pre-login “invite on its way” page—that page uses built-in copy, not your published info screen. Use Welcome or chain from another screen’s next event until this trigger is wired. |
| Me snoozed | Member is snoozed and taps snooze-related UI (avatar, snooze settings). | — | verified |
| Decline suggestion warning | Warning before declining a suggestion on a public profile. | — | verified |
| Mm inform unmatch | Matchmaker-informed unmatch flow in matches. | — | verified |
| Cred confirmation | During phone or email login when credentials need confirmation messaging. | May include dynamic text params from login. | verified |
| Logout | When the member chooses logout from the top menu. | — | verified |
| Bottom bar | Embedded content for the bottom navigation bar area—not a popup; loaded via get screen lookup. | — | verified |
| Engaged snooze | Delete-account flow when the member is engaged and attempts snooze/delete. | — | verified |
| External auth | Profile settings when external authentication needs explanation. | — | verified |
| Before delete profile | Expected before account deletion confirmation. | — | Inactive (July 2026): Admin-only trigger—the current member app does not recognize this event name when loading published screens, and the delete-account flow uses a built-in confirmation dialog instead. Use Engaged snooze for engaged-member delete warnings, or contact engineering if you need a custom pre-delete screen. |
| Duplication detected | When the server detects a duplicate account registration. | — | verified |
| Me page | Me-tab layout hook—loaded as embedded screen content, not always a blocking popup. | — | verified |
| Desktop variation | Not a user-facing moment—pairs with another screen id for desktop web layout. | Set param to the numeric id of the mobile screen you override. | verified — desktop web lookup |
| Make child primary | Parent settings when switching primary child account. | — | verified |
| Share phone workflow | Unified phone-share / request flow in chat introductions. | Required — one param per step; see table below. | verified — multiple steps share this event |
| Frozen limit reached | verified — Member tries to freeze another suggestion but already holds the maximum allowed frozen rows. | — | Configure an Active info screen with this trigger when your brand uses frozen suggestions. See frozen info screens. |
| Frozen partner unavailable | verified — Member tries to re-activate a frozen suggestion but the partner cannot match right now (inactive, snoozed, or no intro slot). | — | Often explains why re-open failed and may offer to release the frozen row. |
| No available slot | verified — Member tries to re-activate frozen but they have no available introduction slot themselves. | — | Pair with support copy pointing to why no new suggestions. |
Next event types
Configure on Next event / Next event 2 for button 1 and button 2.
| Event type | You configure | Member outcome |
|---|---|---|
| None | Nothing further | Dismiss screen. |
| Generic screen | Another info screen from your brand | Chains to that screen configuration. |
| App screen | Built-in route (home, me, questionnaires, conversation, payments, settings, …) | Standard in-app navigation. |
| Content screen | Published app content record | Static content viewer—not another dynamic screen row. |
| Share | Param string | Native share sheet when supported. |
| Custom | Action name (logout, share, break the ice, chat now, …) | Runs named handler in app code. |
| Group | User group | May attach member to group (eligibility rules apply on automated paths). |
| Element | Me-tab element (premium, tasks, questionnaire, insight, settings, customer support, …) | Focuses Me page section. |
| Back office link | Operator link template | WebView navigation for matchmaker tools. |
| Comm trigger | Trigger or cancel comm | Pairs with communication templates from questionnaire post-actions. |
| Lambda | Param passed to server function | Server-side custom action—common on questionnaire answers, rare on standalone screens. |
How the app picks a screen
- On launch the app downloads published screens JSON for the member’s language.
- When a trigger fires, the app searches for rows where event matches, param is empty or equals the runtime param, and platforms includes the current device (or platforms list is empty).
- The first matching published screen wins. If several rows match, ordering depends on JSON array order—keep one active screen per event/param/platform combination to avoid surprises.
- Popup, curtain, and instruction types show as overlays; full screen, slider, cards, menu, grid, and content types push a dedicated route. Tabs Screen is listed in Admin but is not production-ready in the current member app—see Inactive triggers and types.
- If no screen matches, the app runs any fallback callback (for example continue login) without showing your content.
Analytics: Showing a screen logs a dynamic screen viewed event with the screen id and type for reporting.
Inactive triggers and types
Do not publish Active screens that depend on these until product or engineering confirms they are live for your brand.
| Admin option | What happens today | Workaround |
|---|---|---|
| Tabs Screen (type) | No tab editor in Admin; member app tab page is not wired to published JSON. | Menu Screen (vertical list with per-row actions) or Grid Screen (tile hub). Split topics into separate screens chained with Generic screen next events. |
| Pre login end (trigger) | Pre-login completion uses a hard-coded member-app page—the app does not look up a published screen for this trigger. | Welcome for signed-out flows, or open your screen manually from another screen’s button via Generic screen. |
| Before delete profile (trigger) | Event exists in Admin only—the member app enum omits it, so published JSON cannot match. Delete flow shows a built-in confirmation dialog. | Engaged snooze when the member is engaged and tries to delete. For general delete copy, use comms or app-content until the trigger is implemented. |