Skip to content

Add Download app promo banner on desktop upload expense flow #61885

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
May 29, 2025

Conversation

nyomanjyotisa
Copy link
Contributor

@nyomanjyotisa nyomanjyotisa commented May 13, 2025

Explanation of Change

Fixed Issues

$ #61422
PROPOSAL: #61422 (comment)

Tests

Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Test 1

  1. Log in to an account that has not logged in to the native app before
  2. Click on FAB -> Create expense
  3. On desktop version, verify that the Download app promo banner displayed correctly

Test 2

  1. Log in to an account that has previously logged in to the native app
  2. Click on FAB -> Create expense
  3. On desktop version, verify that the Download app promo banner is not displayed
  • 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
    • MacOS: Desktop
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 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 image
Android: mWeb Chrome image
iOS: Native

image

iOS: mWeb Safari

image

MacOS: Chrome / Safari

User without the app installed / not logged in

MacOS-Chrome.mp4

User with the app installed / logged in

MacOS-Chrome-2.mp4
MacOS: Desktop

User without the app installed / not logged in

MacOS-Desktop.mp4

User with the app installed / logged in

MacOS-Desktop-2.mp4

@nyomanjyotisa
Copy link
Contributor Author

I've started a new Slack discussion here to confirm the translation

@nyomanjyotisa nyomanjyotisa marked this pull request as ready for review May 13, 2025 03:06
@nyomanjyotisa nyomanjyotisa requested a review from a team as a code owner May 13, 2025 03:06
@melvin-bot melvin-bot bot requested review from mananjadhav and removed request for a team May 13, 2025 03:06
Copy link

melvin-bot bot commented May 13, 2025

@mananjadhav 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]

@dubielzyk-expensify
Copy link
Contributor

dubielzyk-expensify commented May 13, 2025

Sorry if my issue was poorly explained, but I think we'd wanna show it on Desktop web as well:
image

Here it's not showing 🤔 @jamesdeanexpensify @Expensify/design for visibility

@nyomanjyotisa
Copy link
Contributor Author

I’ve updated the PR to include desktop web as well

@jamesdeanexpensify
Copy link
Contributor

Just so I'm clear - where are we going to add this? Web, mobile web, and desktop? I feel like we add it to everywhere but the mobile app, personally, but curious for thoughts!

@shawnborton
Copy link
Contributor

That makes sense, and I feel pretty strongly we shouldn't show this to users who already have the apps installed.

@jamesdeanexpensify
Copy link
Contributor

Agreed!

@dannymcclain
Copy link
Contributor

I feel pretty strongly we shouldn't show this to users who already have the apps installed

Agree, especially if there's no way to dismiss it.

@dubielzyk-expensify
Copy link
Contributor

The reason why I didn't wanna push for mobile is the UI for mobile web is different:

image

The UI above leads little room for that banner unless we wanna rejigger stuff. Plus that sometimes iOS and Android show that "Download app" banner at the top of the page.

@jamesdeanexpensify
Copy link
Contributor

Ah, fair! So just desktop and web web then? Or what do you call it when you are on a computer and go on the world wide web? Just web?

@dubielzyk-expensify
Copy link
Contributor

Desktop app and desktop web 😄 I do like web web too though 😂❤️

@@ -968,6 +970,24 @@ function IOURequestStepScan({
receiptImageTopPosition={receiptImageTopPosition}
/>
)}
{platform !== CONST.PLATFORM.MOBILEWEB && !isMobile() && (
Copy link
Collaborator

Choose a reason for hiding this comment

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

@nyomanjyotisa It would be better to have this in platform specific files.

@mananjadhav
Copy link
Collaborator

@nyomanjyotisa Can you please resolve the conflicts?

@nyomanjyotisa
Copy link
Contributor Author

PR updated and retested. Also, what is the final decision regarding the button styling here?

Small Size Normal Size
image image

cc @mananjadhav @dubielzyk-expensify

@shawnborton
Copy link
Contributor

I like the small button, but that orphan on the copy is killing me. Maybe we can add a word or two so the sentence feels more balanced? "Scan receipts directly from your phone" or something?

@jamesdeanexpensify
Copy link
Contributor

Scan receipts from your phone work?

@nyomanjyotisa
Copy link
Contributor Author

Here is the comparison for both copy

image image

@jamesdeanexpensify
Copy link
Contributor

I think Scan receipts from your phone works!

@dubielzyk-expensify
Copy link
Contributor

LGTM 👍

@@ -977,6 +993,25 @@ function IOURequestStepScan({
receiptImageTopPosition={receiptImageTopPosition}
/>
)}
{!isMobile() && isLastAppLoginLoaded && !hasInstalledApp && (
Copy link
Collaborator

Choose a reason for hiding this comment

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

With these many changes and checks, I think it makes sense to make it a resuable component.

Copy link
Collaborator

@mananjadhav mananjadhav left a comment

Choose a reason for hiding this comment

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

Left a few comments.

@nyomanjyotisa
Copy link
Contributor Author

PR updated

import ONYXKEYS from '@src/ONYXKEYS';

const useHasInstalledApp = () => {
const [lastIOSLogin] = useOnyx(ONYXKEYS.NVP_LAST_ECASH_IOS_LOGIN, {canBeMissing: true});
Copy link
Collaborator

Choose a reason for hiding this comment

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

@nyomanjyotisa We should use const [lastIOSLogin, lastIOSLoginResult] = useOnyx(ONYXKEYS.NVP_LAST_ECASH_IOS_LOGIN, {canBeMissing: true}); and get rid of the setTimeout.

const [isLastAppLoginLoaded, setIsLastAppLoginLoaded] = useState(false);

useEffect(() => {
const timer = setTimeout(() => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

As I mentioned earlier this isn't needed, we should rely on loaded/loading status from useOnyx hook.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

PR updated!

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you post revised screenshots based on these changes? To esnure it doesn't have any flicker or something.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, I've updated the screenshots

@mananjadhav
Copy link
Collaborator

mananjadhav commented May 23, 2025

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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 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 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)
  • 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
  • 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.
  • 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.
  • 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
Android: mWeb Chrome mweb-chrome-download-banner
iOS: HybridApp ios-show-download-banner
iOS: mWeb Safari
mweb-safari-hide-download-banner.mov
MacOS: Chrome / Safari
web-show-download-banner.mov

web-hide-download-banner

MacOS: Desktop
desktop-show-download-banner.mov

Copy link
Collaborator

@mananjadhav mananjadhav left a comment

Choose a reason for hiding this comment

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

Issues with my Android setup. Tests well. Uploaded screenshots for rest of the platforms.

@melvin-bot melvin-bot bot requested a review from puneetlath May 23, 2025 19:55
@mananjadhav
Copy link
Collaborator

Quick bump @puneetlath

src/ONYXKEYS.ts Outdated
Comment on lines 530 to 534
/** Timestamp of the last login on iOS */
NVP_LAST_ECASH_IOS_LOGIN: 'nvp_lastECashIOSLogin',

/** Timestamp of the last login on Android */
NVP_LAST_ECASH_ANDROID_LOGIN: 'nvp_lastECashAndroidLogin',
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should also add the lastAndroidLogin and lastiPhoneLogin nvps here. Since those are also for our mobile apps.

@@ -977,6 +978,7 @@ function IOURequestStepScan({
receiptImageTopPosition={receiptImageTopPosition}
/>
)}
{!isMobile() && <DownloadAppBanner />}
Copy link
Contributor

Choose a reason for hiding this comment

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

Generally, we should be avoiding using isMobile() checks and instead having a separate index.web.ts and index.ts file, no?

Copy link
Collaborator

@mananjadhav mananjadhav May 27, 2025

Choose a reason for hiding this comment

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

@puneetlath Here I felt it was okay because we don't want to show on Mobile Web as well as Native app. Even if we did add index.web.ts, we'll need to add a check for isMobile to hide it on mWeb.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, in this case, we do need the isMobile checks for mWeb

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok that makes sense to me. Can we add a comment explaining why we are using it here?

import {useOnyx} from 'react-native-onyx';
import ONYXKEYS from '@src/ONYXKEYS';

const useHasInstalledApp = () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a suggestion to make this even more explicit to what it is.

Suggested change
const useHasInstalledApp = () => {
const useHasLoggedIntoMobileApp = () => {


const isLastAppLoginLoaded = lastIOSLoginResult.status !== 'loading' && lastAndroidLoginResult.status !== 'loading';

const hasInstalledApp = !!lastIOSLogin || !!lastAndroidLogin;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const hasInstalledApp = !!lastIOSLogin || !!lastAndroidLogin;
const hasLoggedIntoMobileApp = !!lastIOSLogin || !!lastAndroidLogin;

const [lastIOSLogin, lastIOSLoginResult] = useOnyx(ONYXKEYS.NVP_LAST_ECASH_IOS_LOGIN, {canBeMissing: true});
const [lastAndroidLogin, lastAndroidLoginResult] = useOnyx(ONYXKEYS.NVP_LAST_ECASH_ANDROID_LOGIN, {canBeMissing: true});

const isLastAppLoginLoaded = lastIOSLoginResult.status !== 'loading' && lastAndroidLoginResult.status !== 'loading';
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const isLastAppLoginLoaded = lastIOSLoginResult.status !== 'loading' && lastAndroidLoginResult.status !== 'loading';
const isLastMobileAppLoginLoaded = lastIOSLoginResult.status !== 'loading' && lastAndroidLoginResult.status !== 'loading';

@mananjadhav
Copy link
Collaborator

@nyomanjyotisa Can you fix the conflicts? and also look at the comments.

@nyomanjyotisa
Copy link
Contributor Author

PR updated and retested

Copy link
Collaborator

@mananjadhav mananjadhav left a comment

Choose a reason for hiding this comment

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

Thanks for the update @nyomanjyotisa. Test the latest change again.

@puneetlath All yours.

@melvin-bot melvin-bot bot requested a review from puneetlath May 28, 2025 02:46
Copy link
Contributor

@puneetlath puneetlath left a comment

Choose a reason for hiding this comment

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

Almost there!

@@ -977,6 +978,7 @@ function IOURequestStepScan({
receiptImageTopPosition={receiptImageTopPosition}
/>
)}
{!isMobile() && <DownloadAppBanner />}
Copy link
Contributor

Choose a reason for hiding this comment

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

Ok that makes sense to me. Can we add a comment explaining why we are using it here?

import {useOnyx} from 'react-native-onyx';
import ONYXKEYS from '@src/ONYXKEYS';

const useHasLoggedIntoMobileApp = () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add a comment explaining what this hook does? Like that it returns whether the user has ever logged into one of the Expensify mobile apps.

@nyomanjyotisa
Copy link
Contributor Author

PR updated!

Copy link
Collaborator

@mananjadhav mananjadhav left a comment

Choose a reason for hiding this comment

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

Thanks @puneetlath.

Thanks for the updates @nyomanjyotisa.

@melvin-bot melvin-bot bot requested a review from puneetlath May 29, 2025 02:40
@puneetlath puneetlath merged commit d7cce43 into Expensify:main May 29, 2025
17 checks passed
@OSBotify
Copy link
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.

Copy link
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.1.54-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Copy link
Contributor

github-actions bot commented Jun 2, 2025

🚀 Deployed to production by https://github.com/roryabraham in version: 9.1.54-7 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 success ✅

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.

8 participants