-
Notifications
You must be signed in to change notification settings - Fork 240
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
feat: Force user to go through onboarding steps for every registration #4014
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Either we retro-fix the missing action for existing users, or check the |
@sshanzelI tried creating an user where I skipped tags and settings, then I tried using "useFeedSettings" and both tags and advanced settings is filled with a lot of default stuff. So not sure we can check that way |
If you skip the tags part, the |
For reference to anyone reading, responded to this here |
Anyone who created an account before this date is exempt from the requirement. | ||
*/ | ||
const registeredBeforeRequired = | ||
user?.createdAt && new Date(user.createdAt) < new Date('2025-01-08'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will have to match exactly release right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rebelchris Not necessarily. If we want to give time for the extension to get published and stuff, we could just set the date a few days in the future. We don't necessarily have to start redirecting users exactly on merge date.
And new extension installs will have to install the newest version, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, and do you redirect extension as well?
I'm not sure i'm seeing that part now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then it's fine, maybe we'll need to check with Ido what he thinks on extension vs non extension usage here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of redirecting immediately can we use the "hijacking" page (or whatever it's called) with slightly different copy and on click it redirects to onboarding? I already see the hate of us auto redirecting and users losing focus
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@idoshamun Not entirely sure what you are referencing here. This is not supposed to affect existing users, and users trying to skip it should never have access to the rest of the page anyway, so they shouldn't really notice the redirecting.
chrome_MspWbpuF2k.mp4
Also, on the extension part, you can't access the extension without logging in, right? So users who installed and registered after the given date should not be able to bypass the onboarding in any way, webapp or extension.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm talking specifically on extension, automatically redirecting the extension to onboarding page will lead to complaints that i'd like to avoid. Try to use the extension without being logged in and you'll see the solution i'm referring to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm talking specifically on extension, automatically redirecting the extension to onboarding page will lead to complaints that i'd like to avoid. Try to use the extension without being logged in and you'll see the solution i'm referring to
Alright, I think I'm picking up what you're putting down. You basically want me to show this screen instead on the extension:
Should be able to make that happen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about extension? 👀
@rebelchris Do you have a suggested cutoff date? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, but it's a super, super sensitive flow.
Can we maybe do a sync where you can show me flows from extension and webapp?
Rather double sanity check this then just rolling it out 🙏
(@sshanzel FYI, you might also want to look)
const isOnboardingComplete = | ||
isOnboardingReady && hasCompletedEditTags && hasCompletedContentTypes; | ||
const shouldRedirectOnboarding = | ||
isPageReady && (!user || !isOnboardingComplete) && !isTesting; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this affect current users now? (I didn't test it)
Changes
This should prevent the user from refreshing to skip the necessary steps. Users created before the given date (currently 08-01-2 5) will not be required to complete the onboarding
Events
Did you introduce any new tracking events?
Experiment
Did you introduce any new experiments?
Manual Testing
Caution
Please make sure existing components are not breaking/affected by this PR
MI-700 #done
Preview domain
https://mi-700.preview.app.daily.dev