Skip to content

[Due for payment 2026-08-29] [$250] Add persistent bottom-right product marketing window #95791

Closed
1 of 1 issue completed

Description

@JmillsExpensify

Related: https://github.com/Expensify/Expensify/issues/656359

Background

Today, in-app product marketing is mostly two surfaces: the Announcements slot on Home, and Concierge harpoons. Both share the same core problem — they disappear from view without explicit user action. Announcements only lives on Home, so it's invisible everywhere else in the app, and harpoons compete for space with support and other Concierge messages.

This initiative introduces a persistent bottom-right window that stays visible across the app, on web and mobile, regardless of which page the user is on, until they explicitly dismiss it. This gives us a reliable framework for monthly product updates and targeted feature reach-outs, and improves our odds of reaching a user while their interest in a given feature is active.

Scope

  • Add a persistent, dismissible window anchored to the bottom-right of the app.
  • The window remains visible across page navigation within the app until the user dismisses it.
  • Support a single active window at a time (no stacking/queueing in this release).
  • Each window includes an image/illustration, a heading, supporting body copy, a primary CTA, and a Dismiss action.
  • Once dismissed, the window does not reappear for that specific announcement.
  • Support audience-based targeting so a given announcement's content can vary by the user's role.
  • Never show the window at the same time as a centered modal; the modal always takes precedence.

Product and design details

Image

Placement and persistence

The window renders fixed to the bottom-right corner of the app, above other page content, and persists across navigation — moving from Home to Spend to Workspaces, for example, does not dismiss it. It remains until the user taps Dismiss or completes the primary CTA.

Anatomy

Each window follows a consistent template:

  • Visual: an illustration or product screenshot representative of the feature being promoted.
  • Heading: short, bolded (e.g. "Upload your expense policy PDF").
  • Body copy: 1–2 sentences describing the feature and its benefit (e.g. "Admins can now upload a PDF of their expense policy directly to their workspace, making it visible to all employees in one place.").
  • Primary CTA: green pill button that routes the user to the relevant feature or flow (e.g. Try it out).
  • Secondary action: a Dismiss button that closes the window.

Dismissal behavior

Dismissal is scoped per announcement: tapping Dismiss closes the window for that specific announcement only. A subsequent monthly update or feature reach-out is a new announcement, so it can still surface even if the user dismissed a prior one.

Content source

Content for each window is authored by the marketing team per in-product update — image/illustration, heading, body copy, and CTA destination are all supplied by marketing for each release, not generated dynamically.

Audience targeting

A single announcement can carry different content depending on the user's role, so marketing can promote the most relevant feature to each audience rather than a one-size-fits-all message. Role is evaluated as follows:

  • Member only (not an admin on any workspace): sees the member-targeted variant.
  • Admin (admin on at least one workspace): sees the admin-targeted variant.
  • Both (member on some workspaces, admin on others): admin prevails — the user sees the admin-targeted variant.

Each announcement therefore needs, at minimum, a member variant and an admin variant of the heading/body/CTA; marketing supplies both when authoring the announcement.

Precedence vs. centered modal

The bottom-right window and a centered modal are never shown simultaneously. If both are eligible at the same time, the centered modal takes precedence and the window does not render until the modal is dismissed or its condition no longer applies.

Examples

  • An admin is on the Spend page when a new monthly update ships; the window appears bottom-right without interrupting their current task.
  • The admin navigates from Spend to Workspaces; the window remains visible in the same position.
  • A workspace member (no admin role anywhere) sees the member-targeted variant of an announcement; an admin sees the admin-targeted variant of the same announcement.
  • A user who is a member of Workspace A and an admin of Workspace B sees the admin-targeted variant, since admin prevails.
  • The admin taps Try it out on an "Upload your expense policy PDF" window; they're routed to the relevant settings page.
  • The admin taps Dismiss instead; the window closes for that announcement, but a future announcement (e.g. next month's update) can still appear.
  • A centered modal becomes eligible while the bottom-right window is already showing: the centered modal takes precedence and the window is suppressed until the modal is dismissed.

Assigning to @danielrvidal to help push it forward from here.

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @huult

Activity

  1. PiyushChandra17 commented on Jul 10, 2026

    @PiyushChandra17
    Contributor

    @JmillsExpensify I'd like to work on this, if it's open for external contributors. Thanks!

    PS: Everything is already detailed in OP.

  2. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jul 10, 2026
  3. JmillsExpensify commented on Jul 10, 2026

    @JmillsExpensify
    ContributorAuthor

    Sounds good! We will circle back on next steps, going to add the Internal label for now.

  4. JmillsExpensify commented on Jul 10, 2026

    @JmillsExpensify
    ContributorAuthor

    Assigned Jack to help on the internal engineering side.

  5. danielrvidal commented on Jul 10, 2026

    @danielrvidal
    Contributor

    We should be starting to talk about what features will be in the product update so should have more direction then.

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 13, 2026
  7. KJ21-ENG commented on Jul 13, 2026

    @KJ21-ENG
    Contributor

    🚨 Edited by proposal-police: This proposal was edited at 2026-07-13 11:48:44 UTC.

    Proposal

    What is the root cause of that problem?

    The existing product announcements cannot provide this behavior because they are ordinary Home widgets. HomePage mounts AnnouncementSection only inside its narrow and wide Home layouts, so the section unmounts as soon as the user navigates to another tab or screen.

    {shouldUseNarrowLayout ? (
    <>
    <FreeTrialSection />
    <TimeSensitiveSection />
    <GettingStartedSection />
    <ForYouSection />
    <UpcomingTravelSection />
    <RecentlyAddedSection />
    <YourSpendSection />
    <SpendOverTimeSection />
    <DiscoverSection />
    <AnnouncementSection />
    </>
    ) : (
    <>
    <View
    testID="homePageLeftColumn"
    style={styles.homePageLeftColumn}
    >
    <TimeSensitiveSection />
    <GettingStartedSection />
    <ForYouSection />
    <RecentlyAddedSection />
    <SpendOverTimeSection />
    </View>
    <View
    testID="homePageRightColumn"
    style={styles.homePageRightColumn}
    >
    <FreeTrialSection />
    <UpcomingTravelSection />
    <YourSpendSection />
    <DiscoverSection />
    <AnnouncementSection />
    </View>

    The announcement model is also only a static list of title/subtitle/URL/date records, and AnnouncementSection simply opens each URL. There is no single active marketing-card model, member/admin content variants, app-level host, modal-precedence gate, or per-announcement dismissal check.

    App/src/CONST/index.ts

    Lines 8878 to 8903 in 28fe63c

    HOME: {
    // Maximum number of items in TimeSensitiveSection and YourSpendSection. Any extra items are revealed via the expand toggle button.
    SECTION_VISIBLE_LIMIT: 5,
    // Cutoff for the "For You" new-vs-old segment: users whose free trial started on/after this date have the empty section hidden.
    FOR_YOU_NEW_USER_CUTOFF_DATE: '2026-06-26',
    ANNOUNCEMENTS: [
    {
    title: 'More Concierge AI upgrades, plus agent beta',
    subtitle: 'Press release',
    url: 'https://www.businesswire.com/news/home/20260701645763/en/Expensifys-AI-Expands-to-Expense-Automation-Spend-Insights-and-Agents',
    publishedDate: '2026-07-01',
    },
    {
    title: 'Ask Concierge AI: charts, insights & more',
    subtitle: 'Newsletter',
    url: 'https://use.expensify.com/blog/ask-expensify-ai-anything',
    publishedDate: '2026-06-30',
    },
    {
    title: 'AI agents, Concierge upgrades, and smarter card controls',
    subtitle: 'Product update',
    url: 'https://use.expensify.com/blog/expensify-june-2026-product-update',
    publishedDate: '2026-06-24',
    },
    ],

    const announcements = CONST.HOME.ANNOUNCEMENTS.toSorted((a, b) => {
    if (a.publishedDate > b.publishedDate) {
    return -1;
    }
    if (a.publishedDate < b.publishedDate) {
    return 1;
    }
    return 0;
    });
    function AnnouncementSection() {
    const {shouldUseNarrowLayout} = useResponsiveLayout();
    const {translate} = useLocalize();
    const styles = useThemeStyles();
    return (
    <WidgetContainer
    title={translate('homePage.announcements')}
    containerStyles={shouldUseNarrowLayout ? styles.pb2 : styles.pb5}
    >
    {announcements.map((announcement) => (
    <MenuItemWithTopDescription
    key={announcement.title}
    description={announcement.subtitle}
    title={announcement.title}
    titleStyle={styles.textBold}
    onPress={() => Linking.openURL(announcement.url)}
    shouldShowRightIcon
    leftComponent={<DateIcon date={announcement.publishedDate} />}
    wrapperStyle={[styles.alignItemsCenter, shouldUseNarrowLayout ? styles.ph5 : styles.ph8]}
    hasSubMenuItems
    viewMode={CONST.OPTION_MODE.COMPACT}
    rightIconWrapperStyle={styles.pl2}
    shouldCheckActionAllowedOnPress={false}
    />
    ))}
    </WidgetContainer>

    What changes do you think we should make in order to solve the problem?

    1. Add one explicitly active product-marketing announcement configuration, with null meaning that no window is active. Give that announcement a stable ID and member/admin variants containing the marketing-supplied image, heading, body, CTA label, and CTA destination. Do not scan a list for the next non-dismissed announcement: if the one active ID is dismissed, render nothing until a later release replaces it with a new ID. This preserves the requested one-at-a-time behavior without introducing stacking or queueing.

    2. Add a ProductMarketingWindowManager and responsive presentational component to both platform variants of RootNavigatorExtraContent. The authenticated root stack already installs this extra-content host outside the changing route screen, so the window can remain mounted while Home, Spend, Workspaces, and other authenticated routes change. Render it as a fixed/absolute bottom-right card on wide layouts and a safe-area-aware, near-full-width bottom card on narrow layouts, following the supplied design.

    import RootNavigatorExtraContent from '@components/Navigation/RootNavigatorExtraContent';
    import addRootHistoryRouterExtension from '@libs/Navigation/AppNavigator/routerExtensions/addRootHistoryRouterExtension';
    import useNavigationResetOnLayoutChange from '@libs/Navigation/AppNavigator/useNavigationResetOnLayoutChange';
    import createPlatformStackNavigatorComponent from '@libs/Navigation/PlatformStackNavigation/createPlatformStackNavigatorComponent';
    import defaultPlatformStackScreenOptions from '@libs/Navigation/PlatformStackNavigation/defaultPlatformStackScreenOptions';
    import type {PlatformStackNavigationEventMap, PlatformStackNavigationOptions, PlatformStackNavigationState, PlatformStackRouterFactory} from '@libs/Navigation/PlatformStackNavigation/types';
    import type {NavigationProp, NavigatorTypeBagBase, ParamListBase, StaticConfig, TypedNavigator} from '@react-navigation/native';
    import {createNavigatorFactory} from '@react-navigation/native';
    import RootStackRouter from './RootStackRouter';
    import useCustomRootStackNavigatorState from './useCustomRootStackNavigatorState';
    const RootStackNavigatorComponent = createPlatformStackNavigatorComponent('RootStackNavigator', {
    createRouter: addRootHistoryRouterExtension(RootStackRouter as PlatformStackRouterFactory<ParamListBase>),
    defaultScreenOptions: defaultPlatformStackScreenOptions,
    useCustomEffects: useNavigationResetOnLayoutChange,
    useCustomState: useCustomRootStackNavigatorState,
    ExtraContent: RootNavigatorExtraContent,
    });

    import SidePanel from '@components/SidePanel';
    import type {ExtraContentProps} from '@libs/Navigation/PlatformStackNavigation/types';
    import React from 'react';
    function RootNavigatorExtraContent({navigation}: ExtraContentProps) {
    return (
    <>
    {/* On web, the SidePanel is rendered outside of the main navigator so it can be positioned alongside the screen */}
    <SidePanel navigation={navigation} />
    </>
    );
    }
    export default RootNavigatorExtraContent;

    // On mobile platforms, concierge is displayed as a separate page and the tab bar
    // is rendered by the TabNavigator, so there is no extra content to show here.
    function RootNavigatorExtraContent() {
    return null;
    }
    export default RootNavigatorExtraContent;

    1. Resolve the audience with the existing active-admin-workspace selector: use the admin variant whenever useHasActiveAdminPolicies() is true, otherwise use the member variant. Because that hook checks whether any active workspace is administered by the current user, a user who is both a member and an admin correctly receives the admin content.

    function useHasActiveAdminPolicies() {
    const login = useCurrentUserPersonalDetails().login ?? '';
    const selector = (policies: OnyxCollection<Policy>) => hasActiveAdminPoliciesSelector(policies, login);
    const [hasActiveAdminPolicies] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {selector});
    return !!hasActiveAdminPolicies;
    }

    App/src/libs/PolicyUtils.ts

    Lines 1838 to 1847 in 28fe63c

    /** Return active policies where current user is an admin */
    function getActiveAdminWorkspaces(policies: OnyxCollection<Policy> | null, currentUserLogin: string | undefined): Policy[] {
    const activePolicies = getActivePolicies(policies, currentUserLogin);
    return activePolicies.filter((policy) => shouldShowPolicy(policy, getIsOffline(), currentUserLogin) && isPolicyAdmin(policy, currentUserLogin));
    }
    /** Return active policies where current user is an employee (of the role "user") */
    function getActiveEmployeeWorkspaces(policies: OnyxCollection<Policy> | null, currentUserLogin: string | undefined): Policy[] {
    const activePolicies = getActivePolicies(policies, currentUserLogin);
    return activePolicies.filter((policy) => shouldShowPolicy(policy, getIsOffline(), currentUserLogin) && isPolicyUser(policy, currentUserLogin));

    1. Store dismissal under a namespaced key such as productMarketingWindow:<announcementID> in the existing dismissed-product-training NVP. Extend its Onyx type to accept that key pattern, and use dismissProductTraining() for both actions. Dismiss records the active ID and closes the card; the primary CTA records the ID first and then navigates to its configured destination, preventing the card from flashing again during navigation. A future announcement has a different ID and remains eligible.

    function dismissProductTraining(elementName: string, isDismissedUsingCloseButton = false) {
    const date = new Date();
    const dismissedMethod = isDismissedUsingCloseButton ? 'x' : 'click';
    const optimisticData = [
    {
    onyxMethod: Onyx.METHOD.MERGE,
    key: ONYXKEYS.NVP_DISMISSED_PRODUCT_TRAINING,
    value: {
    [elementName]: {
    timestamp: DateUtils.getDBTime(date.valueOf()),
    dismissedMethod,
    },
    },
    },
    ];
    API.write(WRITE_COMMANDS.DISMISS_PRODUCT_TRAINING, {name: elementName, dismissedMethod}, {optimisticData});
    }

    type DismissedProductTrainingElement = {
    /** The timestamp of when the user dismissed the product training element. */
    timestamp: string;
    /** The method of how the user dismissed the product training element, click or x. */
    dismissedMethod: 'click' | 'x';
    };
    /**
    * This type is used to store the timestamp of when the user dismisses a product training ui elements.
    */
    type DismissedProductTraining = {
    /**
    * When user dismisses the nudgeMigration Welcome Modal, we store the timestamp here.
    */
    [CONST.MIGRATED_USER_WELCOME_MODAL]: DismissedProductTrainingElement;
    /**
    * When user dismisses the AI features promo modal, we store the timestamp here.
    */
    [CONST.AI_FEATURES_PROMO_MODAL]: DismissedProductTrainingElement;

    1. Subscribe the manager to ONYXKEYS.MODAL with isModalCoveringSelector() and render nothing while a non-popover covering modal is opening or visible. This conservatively includes centered modals, guarantees they never overlap the marketing window, and lets the still-mounted manager show the card again when the modal state clears.

    const willAlertModalBecomeVisibleSelector = (modal: OnyxEntry<Modal>) => modal?.willAlertModalBecomeVisible;
    const isRHPVisibleSelector = (modal: OnyxEntry<Modal>) => modal?.type === CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED;
    const isModalCoveringSelector = (modal: OnyxEntry<Modal>) => !!modal?.willAlertModalBecomeVisible && !modal?.isPopover;
    const isModalActiveSelector = (modal: OnyxEntry<Modal>) => !!modal?.isVisible || !!modal?.willAlertModalBecomeVisible;

    useEffect(() => {
    let removeOnCloseListener: () => void;
    if (isVisible) {
    shouldCallHideModalOnUnmount.current = true;
    willAlertModalBecomeVisible(true, type === CONST.MODAL.MODAL_TYPE.POPOVER || type === CONST.MODAL.MODAL_TYPE.BOTTOM_DOCKED);
    // To handle closing any modal already visible when this modal is mounted, i.e. PopoverReportActionContextMenu
    if (onClose) {
    removeOnCloseListener = setCloseModal(onClose);
    }
    }
    // When the modal becomes not visible, run dismiss logic to setReadyToFocus after it fully closes.
    if (!isVisible && wasVisible) {
    handleDismissModal();
    }
    return () => {
    if (!removeOnCloseListener) {
    return;
    }
    removeOnCloseListener();
    };
    }, [isVisible, wasVisible, onClose, type, handleDismissModal]);

    Test coverage: add unit tests for single-active selection (including proving that dismissal does not fall through to an older item), member/admin/both audience resolution, and namespaced dismissal. Add component tests proving the window survives route changes, dismisses before CTA navigation, stays hidden after either action, is suppressed and restored around a centered modal, and uses the expected wide and narrow layouts.

    What alternative solutions did you explore? (Optional)

    Extending AnnouncementSection would retain the existing Home-only lifetime and fail cross-app persistence. Mounting the new manager in GlobalModals would make it global, but that host is also initialized for public navigation once startup is ready, so it would require an additional authentication gate; the authenticated root navigator's existing extra-content hook gives the feature the correct lifetime directly.

  8. melvin-bot commented on Jul 13, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani (External)

  9. 103 remaining items

  10. huult commented on Aug 24, 2026

    @huult
    Contributor

    Proposed amount: $500

    Multiple PRs:

    Additional fixes:

    #97960 replaces the generic SetNameValuePair mechanism with a dedicated DismissMarketingWindow command and fixes a stale-client bug where an older client could incorrectly mark a future marketing campaign as “seen” even though it had never been viewed. This introduces a new API contract (DismissMarketingWindow.ts, types.ts, CONST) rather than being a minor fix.

    Scope expansion:

    The review was not limited to the new component. #96141 touched 6 core modal components (BaseModal, ConfirmModal, DecisionModal, FeatureTrainingModal, ExportDownloadStatusModal) to add modal-precedence logic, as well as Onyx import/export state (ImportOnyxStateUtils). #97960 further expanded the work into the API layer with a new command and version-gating logic.

    Test coverage: 20 scenarios

    Verified: #96141 has 11 numbered scenarios + 4 offline test steps = 15; #97960 has 4 test steps + 3 internal QA steps = 7. This gives approximately 22 scenarios in total, so 20 is a reasonable and even slightly conservative figure.

    Files touched:

    47 files in #96141 (including 7 test files) + 10 files in #97960 (including 3 test files), with 1 overlapping file (src/CONST/index.ts) → 56 unique files, including 10 test files.

    #97960 was implemented and released 7 days after the original PR #96141 was released.

  11. JS00001 commented on Aug 24, 2026

    @JS00001
    Contributor

    @huult reviewed an additional PR I put up, so lets update their payment for this issue to $500 please

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Aug 28, 2026
  13. melvin-bot commented on Aug 28, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  14. melvin-bot commented on Aug 31, 2026

    @melvin-bot

    @huult Whoops! This issue is 2 days overdue. Let's get this updated quick!

  15. huult commented on Sep 1, 2026

    @huult
    Contributor
  16. mallenexpensify commented on Sep 1, 2026

    @mallenexpensify
    Contributor

    @huult paid $500, summary updated above. Thx.

  17. JmillsExpensify commented on Sep 6, 2026

    @JmillsExpensify
    ContributorAuthor

    $500 approved for @huult

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorImprovementItem broken or needs improvement.InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions