Skip to content

[Home Page] Getting Started - Hide empty for you#94698

Merged
grgia merged 30 commits into
Expensify:mainfrom
software-mansion-labs:@adamgrzybowski/getting-started-hide-empty-for-you
Jul 9, 2026
Merged

[Home Page] Getting Started - Hide empty for you#94698
grgia merged 30 commits into
Expensify:mainfrom
software-mansion-labs:@adamgrzybowski/getting-started-hide-empty-for-you

Conversation

@adamgrzybowski

@adamgrzybowski adamgrzybowski commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

  • "For You" is now hidden for newly onboarded users until they have a real to-do (submit, approve, export, or pay), then stays visible permanently. Existing users are unaffected.
  • "Getting Started" is promoted to the top-left on web (matching mobile), with a short sub-text under each step's title.
  • "Getting Started" footer copy now shows "Talk to your account executive" for users with an assigned Guide (otherwise "Talk to Concierge"), and the help link opens the #admins room in the RHP.

Fixed Issues

$ #93092
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Sign in as a newly onboarded user with no actionable reports and open Home. Verify the "For You" section is hidden and "Getting Started" appears as the top-left card.
  2. Create/receive a report that needs an action (submit, approve, export, or pay). Verify "For You" now appears, and that it stays visible even after the to-do is cleared.
  3. In "Getting Started", verify each step shows a sub-text line, and that the footer help link ("Talk to your account executive" with a Guide, otherwise "Talk to Concierge") opens the #admins room in the RHP.
  • 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 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)
  • 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)
  • 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.
  • 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
Screen.Recording.2026-06-29.at.17.15.51.mov

@melvin-bot

melvin-bot Bot commented Jun 26, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@adamgrzybowski adamgrzybowski marked this pull request as ready for review June 26, 2026 13:27
@adamgrzybowski adamgrzybowski requested review from a team as code owners June 26, 2026 13:27
@melvin-bot melvin-bot Bot requested a review from trjExpensify June 26, 2026 13:28
@adamgrzybowski adamgrzybowski marked this pull request as draft June 26, 2026 13:28
@melvin-bot melvin-bot Bot requested review from arosiclair and removed request for a team June 26, 2026 13:28
@melvin-bot

melvin-bot Bot commented Jun 26, 2026

Copy link
Copy Markdown

@arosiclair Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c0a91f202d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@adamgrzybowski adamgrzybowski changed the title [Home Page] Getting started - Hide empty for you [Home Page] Getting Started - Hide empty for you Jun 26, 2026
@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@grgia 🦜 🙏

@adamgrzybowski adamgrzybowski marked this pull request as ready for review June 29, 2026 15:09

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6a236a0305

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/pages/home/GettingStartedSection/index.tsx Outdated
@github-actions

Copy link
Copy Markdown
Contributor

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

@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 dce08d9c3e0..958cd6c43f6 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1046,6 +1046,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Firmenkarten verknüpfen',
             setupRules: 'Ausgabelimits einrichten',
             inviteAccountant: 'Lade deine:n Steuerberater:in ein',
+            begin: 'Beginnen',
+            done: 'Fertig',
+            createWorkspaceSubText: 'Workspace bereit für die Einrichtung',
+            connectAccountingSubText: 'Kontenplan und mehr synchronisieren',
+            customizeCategoriesSubText: 'Fügen Sie Ihren Kontenplan hinzu',
+            inviteAccountantSubText: 'Beschleunigen Sie den Monatsabschluss',
+            linkCompanyCardsSubText: 'Auslagen automatisch importieren',
+            setupRulesSubText: 'Belege anfordern, hohe Ausgaben markieren und mehr',
+            needHelp: 'Brauchen Sie Hilfe?',
+            talkToConcierge: 'Mit Concierge chatten',
+            talkToAccountExecutive: 'Sprechen Sie mit Ihrer Kundenbetreuung',
+            forGuidedSetup: 'für die geführte Einrichtung.',
         },
         freeTrialSection: {
             title: ({days}: {days: number}) => `Kostenlose Testversion: Noch ${days} ${days === 1 ? 'Tag' : 'Tage'}!`,
diff --git a/src/languages/es.ts b/src/languages/es.ts
index bc7d6593bb6..dd2878cbe6f 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -1019,6 +1019,17 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Vincular tarjetas corporativas',
             setupRules: 'Configurar reglas de gasto',
             talkToAccountExecutive: 'Habla con tu ejecutivo de cuenta',
+            begin: 'Empezar',
+            done: 'Hecho',
+            createWorkspaceSubText: 'Espacio de trabajo listo para la configuración',
+            connectAccountingSubText: 'Sincroniza tu plan de cuentas y más',
+            customizeCategoriesSubText: 'Añade tu plan de cuentas',
+            inviteAccountantSubText: 'Acelera la contabilidad de fin de mes',
+            linkCompanyCardsSubText: 'Importa gastos automáticamente',
+            setupRulesSubText: 'Solicita recibos, resalta gastos de alto importe y mucho más',
+            needHelp: '¿Necesitas ayuda?',
+            talkToConcierge: 'Habla con Concierge',
+            forGuidedSetup: 'para la configuración guiada.',
         },
         upcomingTravel: 'Próximos viajes',
         upcomingTravelSection: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index cdec1119830..886ac3c2af3 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1062,6 +1062,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Lier des cartes d’entreprise',
             setupRules: 'Configurer les règles de dépense',
             inviteAccountant: 'Inviter votre comptable',
+            begin: 'Commencer',
+            done: 'Terminé',
+            createWorkspaceSubText: 'Espace de travail prêt pour la configuration',
+            connectAccountingSubText: 'Synchronisez votre plan comptable et plus encore',
+            customizeCategoriesSubText: 'Ajoutez votre plan comptable',
+            inviteAccountantSubText: 'Accélérez la comptabilité de fin de mois',
+            linkCompanyCardsSubText: 'Importer automatiquement les dépenses',
+            setupRulesSubText: 'Exiger des reçus, signaler les dépenses élevées, et plus encore',
+            needHelp: 'Besoin d’aide ?',
+            talkToConcierge: 'Parler à Concierge',
+            talkToAccountExecutive: 'Parlez à votre chargé de compte',
+            forGuidedSetup: 'pour la configuration guidée.',
         },
         yourSpend: {
             title: 'Vos dépenses',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index a3aa7af002c..7c391a29ca4 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1060,6 +1060,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Collega carte aziendali',
             setupRules: 'Configura le regole di spesa',
             inviteAccountant: 'Invita il tuo commercialista',
+            begin: 'Inizia',
+            done: 'Fatto',
+            createWorkspaceSubText: 'Spazio di lavoro pronto per la configurazione',
+            connectAccountingSubText: 'Sincronizza il tuo piano dei conti e altro ancora',
+            customizeCategoriesSubText: 'Aggiungi il tuo piano dei conti',
+            inviteAccountantSubText: 'Accelera la contabilità di fine mese',
+            linkCompanyCardsSubText: 'Importa le spese automaticamente',
+            setupRulesSubText: 'Richiedi ricevute, segnala spese elevate e altro ancora',
+            needHelp: 'Hai bisogno di aiuto?',
+            talkToConcierge: 'Parla con Concierge',
+            talkToAccountExecutive: 'Parla con il tuo account executive',
+            forGuidedSetup: 'per la configurazione guidata.',
         },
         yourSpend: {
             title: 'Le tue spese',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index fad628bbb77..ef8646128b2 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1046,6 +1046,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: '会社カードを連携',
             setupRules: '支出ルールを設定',
             inviteAccountant: '会計士を招待',
+            begin: '開始',
+            done: '完了',
+            createWorkspaceSubText: 'ワークスペースのセットアップを開始できます',
+            connectAccountingSubText: '勘定科目表などを同期します',
+            customizeCategoriesSubText: '勘定科目表を追加',
+            inviteAccountantSubText: '月次決算処理をスピードアップ',
+            linkCompanyCardsSubText: '経費を自動で取り込む',
+            setupRulesSubText: '領収書の提出必須設定や高額支出のフラグ付けなどを行えます',
+            needHelp: 'お困りですか?',
+            talkToConcierge: 'Concierge に問い合わせる',
+            talkToAccountExecutive: 'アカウントエグゼクティブに相談する',
+            forGuidedSetup: 'ガイド付きセットアップ用です。',
         },
         yourSpend: {
             title: 'あなたの支出',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index bacbd9f0ac3..5ff12a12704 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1058,6 +1058,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Bedrijfspassen koppelen',
             setupRules: 'Uitgavenregels instellen',
             inviteAccountant: 'Nodig je accountant uit',
+            begin: 'Begin',
+            done: 'Klaar',
+            createWorkspaceSubText: 'Werkruimte klaar voor configuratie',
+            connectAccountingSubText: 'Synchroniseer je rekeningschema en meer',
+            customizeCategoriesSubText: 'Voeg je grootboekschema toe',
+            inviteAccountantSubText: 'Versnel de maandafsluiting',
+            linkCompanyCardsSubText: 'Importeer uitgaven automatisch',
+            setupRulesSubText: 'Vereis bonnen, markeer hoge uitgaven en meer',
+            needHelp: 'Hulp nodig?',
+            talkToConcierge: 'Praat met Concierge',
+            talkToAccountExecutive: 'Praat met je accountmanager',
+            forGuidedSetup: 'voor begeleide installatie.',
         },
         yourSpend: {
             title: 'Je uitgaven',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 56cc410a07f..29a7e23837a 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1060,6 +1060,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Połącz firmowe karty',
             setupRules: 'Skonfiguruj zasady wydatków',
             inviteAccountant: 'Zaproś swojego księgowego',
+            begin: 'Rozpocznij',
+            done: 'Gotowe',
+            createWorkspaceSubText: 'Miejsce pracy gotowe do konfiguracji',
+            connectAccountingSubText: 'Synchronizuj swój plan kont i więcej',
+            customizeCategoriesSubText: 'Dodaj swój plan kont',
+            inviteAccountantSubText: 'Przyspiesz księgowanie na koniec miesiąca',
+            linkCompanyCardsSubText: 'Importuj wydatki automatycznie',
+            setupRulesSubText: 'Wymagaj paragonów, oznaczaj duże wydatki i nie tylko',
+            needHelp: 'Potrzebujesz pomocy?',
+            talkToConcierge: 'Porozmawiaj z Concierge',
+            talkToAccountExecutive: 'Porozmawiaj ze swoim opiekunem klienta',
+            forGuidedSetup: 'z prowadzeniem konfiguracji.',
         },
         yourSpend: {
             title: 'Twoje wydatki',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 47b2bb09044..e3c3db45268 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1058,6 +1058,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: 'Vincular cartões corporativos',
             setupRules: 'Configurar regras de gasto',
             inviteAccountant: 'Convide seu contador',
+            begin: 'Começar',
+            done: 'Concluído',
+            createWorkspaceSubText: 'Espaço de trabalho pronto para configuração',
+            connectAccountingSubText: 'Sincronize seu plano de contas e muito mais',
+            customizeCategoriesSubText: 'Adicione seu plano de contas',
+            inviteAccountantSubText: 'Acelere o fechamento contábil do mês',
+            linkCompanyCardsSubText: 'Importar despesas automaticamente',
+            setupRulesSubText: 'Exigir recibos, sinalizar gastos altos e muito mais',
+            needHelp: 'Precisa de ajuda?',
+            talkToConcierge: 'Falar com o Concierge',
+            talkToAccountExecutive: 'Fale com seu executivo de contas',
+            forGuidedSetup: 'para configuração guiada.',
         },
         yourSpend: {
             title: 'Seus gastos',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 0b46b7513ae..ca8b0d38028 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1029,6 +1029,18 @@ const translations: TranslationDeepObject<typeof en> = {
             linkCompanyCards: '关联公司卡',
             setupRules: '设置消费规则',
             inviteAccountant: '邀请你的会计',
+            begin: '开始',
+            done: '完成',
+            createWorkspaceSubText: '工作区已准备好进行设置',
+            connectAccountingSubText: '同步您的会计科目表等信息',
+            customizeCategoriesSubText: '添加科目表',
+            inviteAccountantSubText: '加快月末核算',
+            linkCompanyCardsSubText: '自动导入报销费用',
+            setupRulesSubText: '要求收据、标记高额支出等',
+            needHelp: '需要帮助吗?',
+            talkToConcierge: '与 Concierge 对话',
+            talkToAccountExecutive: '联系您的客户经理',
+            forGuidedSetup: '以获取引导式设置。',
         },
         yourSpend: {title: '您的支出', awaitingApproval: '等待审批', repaidLast30Days: '过去30天内已偿还', recentTransactions: ({lastFour}: {lastFour: string}) => `最近交易 • ${lastFour}`},
         seeMore: ({count}: {count: number}) => `再查看 ${count} 个`,

Note

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

View workflow run

Comment thread src/libs/actions/Todos.ts Outdated
Comment thread src/pages/home/ForYouSection/shouldHideForYouSection.ts Outdated
@github-actions

This comment has been minimized.

@grgia grgia left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nothing major, I ran the workflows

@flaviadefaria flaviadefaria requested review from flaviadefaria and removed request for trjExpensify June 29, 2026 19:20
@flaviadefaria

Copy link
Copy Markdown
Contributor

@adamgrzybowski I noticed that Getting started is also above Time-sensitive. It should be below Time-sensitive, like it is on mobile. We’re only moving Getting started above For you.

Can you also confirm that clicking Talk to your account executive/Concierge opens #admins in the RHP?

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@flaviadefaria confirming it opens #admins in RHP ✅

@codecov

codecov Bot commented Jun 30, 2026

Copy link
Copy Markdown

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/CONST/index.ts 94.81% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/libs/actions/Todos.ts 100.00% <100.00%> (ø)
src/pages/home/ForYouSection/index.tsx 100.00% <100.00%> (ø)
...ages/home/ForYouSection/shouldHideForYouSection.ts 100.00% <100.00%> (ø)
...s/home/GettingStartedSection/GettingStartedRow.tsx 100.00% <100.00%> (ø)
...tingStartedSection/hooks/useGettingStartedItems.ts 100.00% <ø> (ø)
src/pages/home/HomePage.tsx 100.00% <ø> (ø)
src/styles/index.ts 60.30% <ø> (ø)
src/pages/home/GettingStartedSection/index.tsx 93.33% <90.47%> (-6.67%) ⬇️
... and 153 files with indirect coverage changes

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@grgia I guess we need to wait for backend changes for the new NVP to test it fully

@grgia

grgia commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

@adamgrzybowski yep, next auth deploy. Did you make the nvp setting change?

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (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 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • 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)
    • Any 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)
    • All JSX used for rendering exists in the render method
    • The 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
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
2026-07-07.17.21.27.mov
Android: mWeb Chrome
2026-07-07.17.28.53.mov
iOS: HybridApp
2026-07-07.17.21.27.mov
iOS: mWeb Safari
2026-07-07.17.28.53.mov
MacOS: Chrome / Safari
2026-07-07.17.16.00.mov
2026-07-07.17.12.22.mov

@flaviadefaria

Copy link
Copy Markdown
Contributor

Looking good! Once those final changes are done, I believe we can merge.

flaviadefaria
flaviadefaria previously approved these changes Jul 7, 2026
The Getting Started row only needs the default Button import; no changes to the ButtonComposed barrel export are required for this PR.
@adamgrzybowski adamgrzybowski dismissed stale reviews from flaviadefaria and grgia via 44212ae July 8, 2026 10:56
Match the Concierge link to supporting label size and add vertical padding so it is easier to tap without mis-clicking the last onboarding row.
@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach shoul be fixed

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

This has been fixed, but the fix does not cover the entire text 😅

2026-07-08.14.35.38.mov

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach, the blue part should be clickable, right?

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

@ZhenjaHorbach, the blue part should be clickable, right?

Blue, yes
But it's a bit confusing because when you click near the help text, it opens a screen that's completely unrelated to the text 😅

Wrap the entire need-help line in a pressable so users can open #admins without aiming at the link text alone.
@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach I just made the whole text clickable to make sure that doesn't happen

@ZhenjaHorbach

ZhenjaHorbach commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Sorry for the confusion 😅
I was thinking of leaving the gray text not clickable
But so that it wouldn't be covered by the last onboarding item
That is, make it the same height as the blue text wrapper
But not clickable

@adamgrzybowski

Copy link
Copy Markdown
Contributor Author

@flaviadefaria, we have a small problem shown here #94698 (comment)

Press area behaves weirdly on mobile web. I am trying to figure out the root cause, but it may be a rabbit hole.

So far, the most reliable and simplest solution would be to make the whole text pressable, not only the blue text.

Do you think that would be okay from the product perspective?

@flaviadefaria

Copy link
Copy Markdown
Contributor

So far, the most reliable and simplest solution would be to make the whole text pressable, not only the blue text.
Do you think that would be okay from the product perspective?

Yes, I think that's totally fine!

@dannymcclain

Copy link
Copy Markdown
Contributor

Agree with Flavia 👍

@grgia grgia merged commit c4278b4 into Expensify:main Jul 9, 2026
36 checks passed
@OSBotify

OSBotify commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.4.33-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review — changes required ✅

This PR changes when the For you section renders on Home (hidden for newly onboarded users until their first submit/approve/export/pay to-do, then permanently visible). That contradicts the current Expensify Home Overview article, which states the section always appears and only "may appear empty."

I opened a draft help site PR to fix it: #95842

What the docs PR updates
  • How the For you section works on Home — notes the section stays hidden for recently created accounts until the first to-do appears, then remains on Home.
  • New FAQ — Why don't I see the For you section at all? — covers the new-user hidden state.

Not documented (intentional): the Getting started changes in this PR (top-left placement on web, per-step sub-text, and the "Need help? Talk to Concierge / Talk to your account executive" footer) are cosmetic/layout refinements that don't change the section's documented purpose or appearance conditions, so no article update was needed.


@adamgrzybowski, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

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.

7 participants