Skip to content

Global nav bar POC and Spend/Workspace layout refinements#91955

Draft
shawnborton wants to merge 16 commits into
mainfrom
shawn-globalNavBar
Draft

Global nav bar POC and Spend/Workspace layout refinements#91955
shawnborton wants to merge 16 commits into
mainfrom
shawn-globalNavBar

Conversation

@shawnborton
Copy link
Copy Markdown
Contributor

@shawnborton shawnborton commented May 28, 2026

Explanation of Change

This PR is a design/UX POC bundling several layout and styling refinements. Highlights:

  • Global nav bar: Adds a 48px top bar (wide layout only) with ghost buttons for "Find anything..." (Cmd+K) and "Ask Concierge", plus the account avatar. Persists a 1px bottom border whenever an LHN-bearing navigator is in the active state (including under an RHP).
  • Standardized headers: Switches Account, Workspace editor, and Domain editor pages to the larger topBarLabel (Expensify New Kansas) header font with truncation. Removes illustrations from those headers.
  • Centered max-width layouts: Applies cardMaxWidth: 760 / contentMaxWidth: 1140 to Account, Workspace, and Domain pages so content is centered on wide screens with 20px padding.
  • Full-bleed Spend tables: Table headers, group headers (Member/Card/WithdrawalID), expanded rows, and report transactions use appBG, no border radius, and 20px horizontal padding.
  • Cmd+K search router refinements: 8px horizontal / 8px bottom padding on the list, hidden scrollbar, 12px below the input.
  • Violation labels: Row RBR text (e.g. "Report contains expenses with violations", "Missing category") uses textSupporting while keeping the danger-colored icon.
  • PR [WIP] Smaller LHN and collapsable concept #90319 applied as a patch: Smaller LHN widths (320→280 for non-inbox) and a collapsable/peekable Spend sidebar.
  • shouldOffsetForGlobalNavBar: New opt-in prop on ScreenWrapperContainer to subtract the global nav bar height from max/min height — applied across Account and Workspace pages.

Fixed Issues

$
PROPOSAL:

Tests

  1. Sign in on wide layout — verify the new global nav bar appears with Find / Ask Concierge / avatar.
  2. Navigate between Inbox / Spend / Settings — verify the 1px bottom border persists.
  3. Open a chat header's Details RHP from Inbox — verify the border stays visible.
  4. Press Cmd+K — verify the search router opens 80px from top with the new padding and no scrollbar.
  5. Open Account / Workspace editor / Domain editor — verify headers use the New Kansas font, content is centered at cardMaxWidth, and pages don't get cut off at the bottom.
  6. Open a Spend table (Reports, Expenses, Cash accruals, Card accruals, Bank Reconciliation) — verify full-bleed styling and 20px horizontal padding on header / group rows.
  7. Trigger a violation (e.g. expense without category) — verify the RBR text is supporting-colored with a danger icon.
  8. On Spend, toggle the new collapsable sidebar — verify it peeks on hover and animates between expanded/collapsed widths.
  • Verify that no errors appear in the JS console

Offline tests

Same as tests — verify no regressions in the layouts when offline.

QA Steps

Same as tests.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
- [ ] I verified that similar component doesn't exist in the codebase - [ ] I verified that all props are defined accurately and each prop has a `/** comment above it */` - [ ] I verified that each file is named correctly - [ ] I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone - [ ] I verified that the only data being stored in component state is data necessary for rendering and nothing else - [ ] In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes - [ ] For Class Components, any internal methods passed to components event handlers are bound to `this` properly so there are no scoping issues (i.e. for `onClick={this.submit}` the method `this.submit` should be bound to `this` in the constructor) - [ ] I verified that component internal methods bound to `this` are necessary to be bound (i.e. avoid `this.submit = this.submit.bind(this);` if `this.submit` is never passed to a component event handler like `onClick`) - [ ] I verified that all JSX used for rendering exists in the render method - [ ] I verified that each component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

Screenshots/Videosundefined

@OSBotify
Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 162f0d6f43c..5e142a82a02 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7303,8 +7303,8 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
             syncing: 'Mitarbeitende werden synchronisiert',
         },
         emptyDomain: {
-            title: 'Stärken Sie Ihre Sicherheit mit Domains',
-            subtitle: 'Verlangen Sie, dass Mitglieder in Ihrer Domain sich per Single Sign-On anmelden, schränken Sie das Erstellen von Arbeitsbereichen ein und mehr.',
+            title: 'Erhöhen Sie Ihre Sicherheit mit Domains',
+            subtitle: 'Verlangen Sie von Mitgliedern Ihrer Domain die Anmeldung über Single Sign-On, beschränken Sie das Erstellen von Arbeitsbereichen und mehr.',
         },
     },
     getAssistancePage: {
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 96ff1240ee0..211db957185 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -7097,7 +7097,7 @@ ${amount} para ${merchant} - ${date}`,
         },
         emptyDomain: {
             title: 'Mejora tu seguridad con dominios',
-            subtitle: 'Exige que los miembros de tu dominio inicien sesión mediante inicio de sesión único, restrinjan la creación de espacios de trabajo y más.',
+            subtitle: 'Obliga a las personas de tu dominio a iniciar sesión mediante inicio de sesión único, restringe la creación de espacios de trabajo y mucho más.',
         },
     },
     getAssistancePage: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index b4d4ee53075..52445a55434 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2808,9 +2808,9 @@ ${amount} pour ${merchant} - ${date}`,
         title: 'Modifier l’agent',
         agentName: 'Nom de l’agent',
         instructions: 'Écrire des instructions personnalisées',
-        chatWithAgent: 'Discuter avec l\u2019agent',
+        chatWithAgent: 'Discuter avec l’agent',
         copilotIntoAccount: 'Copilote dans le compte',
-        deleteAgent: 'Supprimer l\u2019agent',
+        deleteAgent: 'Supprimer l’agent',
         deleteAgentTitle: 'Supprimer l’agent ?',
         deleteAgentMessage: 'Voulez-vous vraiment supprimer cet agent ? Cette action est irréversible.',
     },
@@ -4413,7 +4413,7 @@ ${amount} pour ${merchant} - ${date}`,
             travelInvoicingPayableAccount: 'Compte fournisseur déplacements',
             hr: 'RH',
             rooms: 'Salons',
-            findDomain: 'Trouver un domaine',
+            findDomain: 'Rechercher un domaine',
             cardAdminAlternateText: 'Gérer les cartes de l’espace de travail.',
             peopleAdminAlternateText: 'Gérez les membres et les workflows d’approbation.',
             paymentsAdminAlternateText: 'Gérer les paiements de workflow.',
@@ -7334,7 +7334,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
         },
         emptyDomain: {
             title: 'Renforcez votre sécurité avec des domaines',
-            subtitle: 'Obligez les membres de votre domaine à se connecter via l’authentification unique, restreignez la création d’espaces de travail, et plus encore.',
+            subtitle: 'Exiger que les membres de votre domaine se connectent via l’authentification unique, restreindre la création d’espaces de travail, et plus encore.',
         },
     },
     getAssistancePage: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 19d77aafcfa..86efad83c04 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2796,8 +2796,8 @@ ${amount} per ${merchant} - ${date}`,
         title: 'Modifica agente',
         agentName: 'Nome agente',
         instructions: 'Scrivi istruzioni personalizzate',
-        chatWithAgent: 'Chatta con l\u2019agente',
-        copilotIntoAccount: 'Copilot nell\u2019account',
+        chatWithAgent: 'Chatta con l’agente',
+        copilotIntoAccount: 'Copilot nell’account',
         deleteAgent: 'Elimina agente',
         deleteAgentTitle: 'Eliminare agente?',
         deleteAgentMessage: 'Sei sicuro di voler eliminare questo agente? Questa azione non può essere annullata.',
@@ -7288,8 +7288,8 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
             syncing: 'Sincronizzazione dipendenti',
         },
         emptyDomain: {
-            title: 'Migliora la tua sicurezza con i domini',
-            subtitle: 'Richiedi ai membri del tuo dominio di accedere tramite accesso Single Sign-On, limita la creazione di space di lavoro e altro ancora.',
+            title: 'Aumenta la tua sicurezza con i domini',
+            subtitle: 'Richiedi ai membri del tuo dominio di accedere tramite single sign-on, limita la creazione di workspace e altro ancora.',
         },
     },
     getAssistancePage: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 81d16745f98..6a90e4e399d 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7255,7 +7255,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             syncing: 'Synchronizowanie pracowników',
         },
         emptyDomain: {
-            title: 'Zwiększ swoje bezpieczeństwo dzięki domenom',
+            title: 'Zwiększ swoje bezpieczeństwo za pomocą domen',
             subtitle: 'Wymagaj od członków swojej domeny logowania jednokrotnym logowaniem (SSO), ograniczaj tworzenie przestrzeni roboczych i nie tylko.',
         },
     },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index fcf4c886028..9fdc78bef93 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7261,10 +7261,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
             syncingModalDescription: 'A primeira conexão pode levar algum tempo. Você será notificado sobre quaisquer erros.',
             syncing: 'Sincronizando funcionários',
         },
-        emptyDomain: {
-            title: 'Aumente sua segurança com domínios',
-            subtitle: 'Exija que os membros do seu domínio façam login via logon único, restrinja a criação de workspaces e muito mais.',
-        },
+        emptyDomain: {title: 'Aumente sua segurança com domínios', subtitle: 'Exija que membros do seu domínio entrem via logon único, restrinja a criação de workspaces e muito mais.'},
     },
     getAssistancePage: {
         title: 'Obter ajuda',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 6edd51e1d39..8d0c564cf3d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -7072,7 +7072,7 @@ ${reportName}
             syncingModalDescription: '首次连接可能需要一些时间。若发生任何错误,我们会通知你。',
             syncing: '正在同步员工',
         },
-        emptyDomain: {title: '通过域名提升安全性', subtitle: '要求您域中的成员通过单点登录登录、限制工作区创建等。'},
+        emptyDomain: {title: '通过域名增强安全性', subtitle: '要求您域中的成员通过单点登录登录、限制工作区创建等。'},
     },
     getAssistancePage: {
         title: '获取帮助',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@codecov
Copy link
Copy Markdown

codecov Bot commented May 28, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/ROUTES.ts 18.28% <100.00%> (+0.07%) ⬆️
src/SCREENS.ts 100.00% <ø> (ø)
src/components/Badge.tsx 97.36% <100.00%> (+0.07%) ⬆️
src/components/Charts/VictoryTheme.ts 100.00% <100.00%> (ø)
src/components/Charts/components/ScatterPoints.tsx 16.66% <100.00%> (ø)
src/components/Charts/utils.ts 80.22% <100.00%> (+0.22%) ⬆️
src/components/FeatureList.tsx 0.00% <ø> (ø)
...yChartRenderer/components/VictoryChartBarGroup.tsx 4.16% <ø> (+0.16%) ⬆️
src/components/HeaderWithBackButton/index.tsx 88.11% <100.00%> (-3.89%) ⬇️
src/components/Icon/chunks/illustrations.chunk.ts 0.00% <ø> (ø)
... and 135 more
... and 11 files with indirect coverage changes

@github-actions
Copy link
Copy Markdown
Contributor

🚧 @shawnborton has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions
Copy link
Copy Markdown
Contributor

🚧 @shawnborton has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown
Contributor

🚧 @shawnborton has triggered a test Expensify/App build. You can view the workflow run here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants