Skip to content

Early discount countdown banner #54901

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 22 commits into from
Jan 24, 2025

Conversation

parasharrajat
Copy link
Member

@parasharrajat parasharrajat commented Jan 7, 2025

Explanation of Change

Fixed Issues

$ #54817
PROPOSAL: #54817 (comment)

Tests

Claiming the first discount

  1. Sign up as a new user
  2. Create a workspace
  3. Go to your onboarding chat or concierge
  4. Verify you can see a countdown timer starting from 24h.
  5. Verify the banner is not dismissable.
  6. Verify click on “Claim offer” takes you to the subscription page.
  7. Verify the subscription page shows the same timer.
  8. Verify that after you add a card, a promoCode of 50% has been applied to your account. Verify

Claiming the second discount

  1. Sign up as a new user
  2. Create a workspace
  3. Modify the NVP firstDayFreeTrial such that it's earlier than 24h. Run this in the console: Onyx.merge("nvp_private_firstDayFreeTrial", "2024-12-21 23:36:00");
  4. Go to your onboarding chat or concierge
  5. Verify you can see a countdown showing days, hours, minutes, and seconds of the time remaining, which should be max 7 days when it starts.
  6. Verify the banner is dismissable.
  7. Verify click on “Claim offer” takes you to the subscription page.
  8. Verify the subscription page shows the same timer.

Period past 8 days

  1. Sign up as a new user
  2. Create a workspace
  3. Modify the NVP firstDayFreeTrial such that it's later than 8 days. Run this in the console: Onyx.merge("nvp_private_firstDayFreeTrial", "2024-12-21 23:36:00");
  4. Verify no banner is shown in the onboarding chat.
  5. Verify no banner is shown in the subscription page.
  6. Verify that in the subscription, we’re showing the usual free trial banner instead.
  • Verify that no errors appear in the JS console

Offline tests

Same as QA steps.

QA Steps

Prerequisites:

  1. Sign up as a new user
  2. Create a workspace.
  3. Create an Expense on the workspace to begin a new trial.

Claiming the first discount

  1. Go to your onboarding chat or concierge.

  2. Verify you can see a countdown timer starting from 24h.

  3. Verify the banner is not dismissable.

  4. Verify that clicking on “Claim offer” takes you to the subscription page.

  5. Verify the subscription page shows the same timer.

  6. [Depends if backend has implemented the changes] Verify that after you add a card, a promoCode of 50% has been applied to your account.

Claiming the second discount

  1. Login with the same account 24 hours from the trial's start.
  2. Go to your onboarding chat or concierge.
  3. Verify you can see a countdown showing days, hours, minutes, and seconds of the time remaining, which should be max 7 days when it starts.
  4. Verify the banner is dismissible.
  5. Verify that clicking on “Claim offer” takes you to the subscription page.
  6. Verify the subscription page shows the same timer.

Period past 8 days

  1. Login with the same account 8 days from the trial's start.
  2. Verify no banner is shown in the onboarding chat.
  3. Verify no banner is shown on the subscription page.
  4. Verify that in the subscription, we’re showing the usual free trial banner instead.
  • 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 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
17.01.2025_15.26.54_REC.mp4
Android: mWeb Chrome
17.01.2025_15.29.45_REC.mp4
iOS: Native
17.01.2025_15.51.53_REC.mp4
iOS: mWeb Safari
17.01.2025_15.52.46_REC.mp4
MacOS: Chrome / Safari
17.01.2025_15.27.39_REC.mp4
MacOS: Desktop
17.01.2025_15.34.37_REC.mp4

@parasharrajat parasharrajat force-pushed the parasharrajat/early-discount branch from 30b7483 to e857669 Compare January 7, 2025 19:23
@parasharrajat parasharrajat force-pushed the parasharrajat/early-discount branch from e857669 to 498fc03 Compare January 13, 2025 11:33
@parasharrajat parasharrajat marked this pull request as ready for review January 15, 2025 22:36
@parasharrajat parasharrajat requested review from a team as code owners January 15, 2025 22:36
@melvin-bot melvin-bot bot requested a review from eVoloshchak January 15, 2025 22:36
Copy link

melvin-bot bot commented Jan 15, 2025

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

@melvin-bot melvin-bot bot removed the request for review from a team January 15, 2025 22:36
@shawnborton
Copy link
Contributor

Let us know when this is ready for design review!

@youssef-lr
Copy link
Contributor

Can we get some screenshots for the design team please?

Copy link
Contributor

🚧 @youssef-lr has triggered a test build. You can view the workflow run here.

@parasharrajat
Copy link
Member Author

Added web. Adding more in sometime.

Copy link
Contributor

@dannymcclain
Copy link
Contributor

A couple things from the screenshots/videos so far:

  • The banner in the chat view should use our row-hover color for the background
    • image
  • I believe the first 50% off offer that's available for 24 hours is not supposed to be dismissible
  • I thought we said the follow-up offer (25% off for 7 days) would be dismissible
    • image

Would love clarification about the offers and which should be dismissible, but the banner color in the chat needs to be updated regardless.

@youssef-lr
Copy link
Contributor

I believe the first 50% off offer that's available for 24 hours is not supposed to be dismissible

That's correct, I believe I had it coded this way. @parasharrajat can you check?

@eVoloshchak
Copy link
Contributor

eVoloshchak commented Jan 22, 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 tests pass on all platforms & I tested again on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • 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 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: Native
Screen.Recording.2025-01-22.at.13.08.44.mov
Android: mWeb Chrome
Screen.Recording.2025-01-22.at.12.29.37.mov
iOS: Native
Screen.Recording.2025-01-22.at.12.23.09.mov
iOS: mWeb Safari
Screen.Recording.2025-01-22.at.12.25.01.mov
MacOS: Chrome / Safari
Screen.Recording.2025-01-22.at.11.25.23.mov
Screen.Recording.2025-01-22.at.11.35.06.mov
MacOS: Desktop
Screen.Recording.2025-01-22.at.12.06.59.mov

Copy link
Contributor

@eVoloshchak eVoloshchak left a comment

Choose a reason for hiding this comment

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

LGTM!

@parasharrajat
Copy link
Member Author

All yours @youssef-lr

Copy link
Contributor

@youssef-lr youssef-lr left a comment

Choose a reason for hiding this comment

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

LGTM! Not merging yet until we deploy some backend code that updates the length of the trial to 30 days.

@youssef-lr youssef-lr changed the title Early discount countdown banner [HOLD] Early discount countdown banner Jan 22, 2025
@parasharrajat
Copy link
Member Author

@youssef-lr I did notice that when we cancel the banner on the onboarding chat, it pops again on reopening that chat.

Do we want to cancel that permanently?

@youssef-lr youssef-lr changed the title [HOLD] Early discount countdown banner Early discount countdown banner Jan 22, 2025
@youssef-lr youssef-lr changed the title Early discount countdown banner [HOLD Web-E #45151] Early discount countdown banner Jan 22, 2025
@youssef-lr youssef-lr changed the title [HOLD Web-E #45151] Early discount countdown banner Early discount countdown banner Jan 24, 2025
@youssef-lr
Copy link
Contributor

@youssef-lr I did notice that when we cancel the banner on the onboarding chat, it pops again on reopening that chat.

It's intentional.

Copy link
Contributor

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.0.90-0 🚀

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

@kavimuru
Copy link

@youssef-lr @parasharrajat How can we set the NVP? Could this be verified internally?

@parasharrajat
Copy link
Member Author

Please use QA steps for testing. You can Do the 24-hour testing and skip the 8-day one. What do you think @youssef-lr?

@youssef-lr
Copy link
Contributor

@kavimuru it's working well, feel free to skip that part, I tested it myself.

Screen.Recording.2025-01-28.at.16.19.59.mov

@youssef-lr
Copy link
Contributor

If you're asking about the promo code NVP, can you give me the email you used for testing? I can check if it has the NVP.

@kavimuru
Copy link

@youssef-lr QA steps are updated now. Should we wait 24 hours to verify the following?

Claiming the second discount

Copy link
Contributor

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.0.90-6 🚀

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

@shubham1206agra
Copy link
Contributor

This PR introduced a style bug, detailed here #58974

@parasharrajat
Copy link
Member Author

parasharrajat commented May 12, 2025

@shubham1206agra How when we didn't even have that button on this PR?

image
image

@shubham1206agra
Copy link
Contributor

@parasharrajat This PR kind of started the bad layout, which caused the bug. Though, I will replace the offending PR to #57092.

@parasharrajat
Copy link
Member Author

I don't understand what you mean by bad layout. It was tested and was working great for the UI at that time. The PR which added the button should change the layout as they want.

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

Successfully merging this pull request may close these issues.

8 participants