Repository navigation
Description
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
Dismissaction. - 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
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
Dismissbutton 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
Spendpage when a new monthly update ships; the window appears bottom-right without interrupting their current task. - The admin navigates from
SpendtoWorkspaces; 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 outon an "Upload your expense policy PDF" window; they're routed to the relevant settings page. - The admin taps
Dismissinstead; 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
- Upwork Job URL: https://www.upwork.com/jobs/~022076629358073920496
- Upwork Job ID: 2076629358073920496
- Last Price Increase: 2026-07-13
Issue Owner
Current Issue Owner: @huultMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
PiyushChandra17 commentedon Jul 10, 2026
@JmillsExpensify I'd like to work on this, if it's open for
external contributors. Thanks!PS: Everything is already detailed in OP.
JmillsExpensify commentedon Jul 10, 2026
Sounds good! We will circle back on next steps, going to add the Internal label for now.
JmillsExpensify commentedon Jul 10, 2026
Assigned Jack to help on the internal engineering side.
danielrvidal commentedon Jul 10, 2026
We should be starting to talk about what features will be in the product update so should have more direction then.
KJ21-ENG commentedon Jul 13, 2026
🚨 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.
HomePagemountsAnnouncementSectiononly inside its narrow and wide Home layouts, so the section unmounts as soon as the user navigates to another tab or screen.App/src/pages/home/HomePage.tsx
Lines 69 to 103 in 28fe63c
The announcement model is also only a static list of title/subtitle/URL/date records, and
AnnouncementSectionsimply 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
App/src/pages/home/AnnouncementSection.tsx
Lines 14 to 49 in 28fe63c
What changes do you think we should make in order to solve the problem?
Add one explicitly active product-marketing announcement configuration, with
nullmeaning 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.Add a
ProductMarketingWindowManagerand responsive presentational component to both platform variants ofRootNavigatorExtraContent. 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.App/src/libs/Navigation/AppNavigator/createRootStackNavigator/index.tsx
Lines 1 to 22 in 28fe63c
App/src/components/Navigation/RootNavigatorExtraContent/index.tsx
Lines 1 to 16 in 28fe63c
App/src/components/Navigation/RootNavigatorExtraContent/index.native.tsx
Lines 1 to 7 in 28fe63c
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.App/src/hooks/useHasActiveAdminPolicies.ts
Lines 10 to 15 in 28fe63c
App/src/libs/PolicyUtils.ts
Lines 1838 to 1847 in 28fe63c
productMarketingWindow:<announcementID>in the existing dismissed-product-training NVP. Extend its Onyx type to accept that key pattern, and usedismissProductTraining()for both actions.Dismissrecords 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.App/src/libs/actions/Welcome/index.ts
Lines 191 to 207 in 28fe63c
App/src/types/onyx/DismissedProductTraining.ts
Lines 18 to 37 in 28fe63c
ONYXKEYS.MODALwithisModalCoveringSelector()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.App/src/selectors/Modal.ts
Lines 6 to 12 in 28fe63c
App/src/components/Modal/BaseModal.tsx
Lines 152 to 174 in 28fe63c
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
AnnouncementSectionwould retain the existing Home-only lifetime and fail cross-app persistence. Mounting the new manager inGlobalModalswould 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.melvin-bot commentedon Jul 13, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani (
External)103 remaining items
huult commentedon Aug 24, 2026
Proposed amount: $500
Multiple PRs:
Additional fixes:
#97960 replaces the generic
SetNameValuePairmechanism with a dedicatedDismissMarketingWindowcommand 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.
JS00001 commentedon Aug 24, 2026
@huult reviewed an additional PR I put up, so lets update their payment for this issue to $500 please
melvin-bot commentedon Aug 28, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Aug 31, 2026
@huult Whoops! This issue is 2 days overdue. Let's get this updated quick!
huult commentedon Sep 1, 2026
cc @mallenexpensify per this comment.
mallenexpensify commentedon Sep 1, 2026
@huult paid $500, summary updated above. Thx.
JmillsExpensify commentedon Sep 6, 2026
$500 approved for @huult