Implement animated WorkspacesListPage and LoungeAccessPage

[roryabraham]

Details

Implements the new animated layouts in WorkpacesListPage and LoungeAccessPage. Since they share a very similar layout, I created some utility components to DRY up code between them.

Note that this code includes a workaround for an animation that's not quite the right aspect ratio. We'll clean this up in a follow-up once we have an animation source in a better aspect ratio.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/300446
$ #23209
$ (partial) #12261

Tests / QA Steps

1. Sign in to an account with lounge access, or on dev hard-code this condition to true and this condition to false.
2. Go to Settings -> Profile and you should see a menu item for Lounge Access. Click on that to open the Lounge access page.
3. Verify it matches the screenshots below.
4. (web/mWeb only) Sign in to an account without lounge access, or on dev hard-code this condition to true.
5. (web/mWeb only) Navigate to /settings/profile/lounge-access in the browser and verify that you now see a full page not found view in the RHP.
6. Delete all your workspaces, or on dev hard-code this condition to true. Verify that you see a feature list for the workspace page that matches the screenshots below.
7. Change your language to Spanish and go back to the workspaces list page. Verify that the feature list now displays in Spanish.
8. Create a workspace if needed, and on dev remove any hard-coded changes.
9. Navigate to Settings -> Workspaces and verify that the workspace list appears below the animations as shown in the screenshots below.

• Verify that no errors appear in the JS console

Offline tests / QA Steps

(narrow screens only)

1. Go to the workspace page
2. Go offline
3. Verify that the offline indicator that appears at the bottom of the screen is the same color as the default app background, not purple.
4. Go to the preferences page
5. Verify that the offline indicator that appears at the bottom of the screen is the same color as the default app background, not bright blue.

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 / Chrome
  • iOS / native
  • iOS / 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • 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 verified the translation was requested/reviewed 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • 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.js 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 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
  • 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)
  • 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(themeColors.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 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.
• 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

iOS.mov

Android

[roryabraham]

There is a minor known issue with the WorkspacePlanet.json animation that shows some lines of magenta during the rotation:

MagentaOverflow.mov

I'm not entirely sure what's causing this but I think it may be intrinsic to the animation itself because that color is not on the view beneath the animation. I don't think this is worth blocking this PR over, and can be addressed in a follow-up.

[roryabraham]

Updated (and fixed a bug in useNetwork). Ready for re-review @Beamanator

[shawnborton]

Looks so good! One thing that I think I missed from the last PR - in the page header, can we make the arrow use the 80% opacity ivory, but the actual header text just use 100% opacity ivory?

[roryabraham]

No problem @shawnborton, here's what that looks like:

I agree that looks a bit better 👍🏼

[roryabraham]

@shawnborton I also fixed this other bug as requested.

[OSBotify]

🧪🧪 Use the links below to test this build in android and iOS. Happy testing! 🧪🧪

android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/23061/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/23061/index.html
desktop 💻	web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/23061/NewExpensify.dmg	https://23061.pr-testing.expensify.com

[shawnborton]

Sweet, thanks!

[roryabraham]

@Beamanator bump for re-review please

[Beamanator]

Looks great to me, nice work @roryabraham !

[OSBotify]

🚀 Deployed to staging by https://github.com/Beamanator in version: 1.3.46-0 🚀

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

[OSBotify]

🚀 Deployed to staging by https://github.com/Beamanator in version: 1.3.47-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.46-2 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/Beamanator in version: 1.3.47-6 🚀

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

[eVoloshchak]

This has caused a small regression in #25433

FullPageNotFoundView isn't wrapped with SafeAreaView, so it was overlapping with the notification bar on Android.
We resolved this by using <NotFoundPage /> instead, which is FullPageNotFoundView wrapped with ScreenWrapper (it has safe area insets)