[Landing Page] Redirect workspace members invited on NewDot #45015
Description
Coming from here.
Problem
We're working towards redirecting 100% of sign-ups to NewDot with the Summer release, yet the people these sign-ups invite to a workspaces can end up with a different experience to the one they're using themselves.
Why is this important?
It creates a confusing dynamic for the inviting admin and their workspace members, as they'll be blissfully unaware of this as they're new to Expensify. For example, if the admin gives the member instructions on how to do something that they can't see, like a reference to a place in the UI that doesn't exist in the platform they're on etc.
Solution
Default to NewDot any new account invited to a workspace on NewDot. This means setting classicRedirect.dismissed to false in the tryNewDot NVP for these invited workspace members. In turn, if they head to expensify.com, they'll be redirected to new.expensify.com. If they download the (then released) HybridApp, we'll load the NewDot native experience, not the OldApp one.
For the avoidance of doubt, any new account invited to a workspace via OldDot should not be defaulted to NewDot at this stage.
CC: @Julesssss @JmillsExpensify @danielrvidal @puneetlath @AndrewGable from the thread. I'm going to track this with the landing page project in #wave-collect, so we have it done at the latest by then when we'll start turning on the tap for all new sign-ups on expensify.com being routed to new.expensify.com. But as discussed in thread, nothing is stopping us doing this right now.