-
Notifications
You must be signed in to change notification settings - Fork 898
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
Better UX for showing pricing section in mobile #894
Comments
@goutham-documenso thoughts on the flow for this? |
@dguyen Scrolling to the pricing card upon selection is a good solution, I'd also make the Switch sticky to the top. That way if the user scrolls to the Early adopter plan area, they'd still be able to see the switch and see the price difference instantly. |
@goutham-documenso We can stack cards as the user scrolls. This could be a good solution as well. |
Please keep in that that at least 1 more (if not more) pricing Tiers will be added soon while implementing |
@goutham-documenso the switch sticky sounds good, can you please provide a design? |
@dguyen I'll share the design shortly. |
@plxity are you good with implementing the above design for mobile? |
Hey there! I know @plxity already mentioned in the issue description that he'd like to work on this but since it's been 1 month since the last comment, I'd like to know if I can work on it. |
@JuanSebastianM, sure! I've reassigned it to you |
Describe the improvement you are suggesting in detail
Currently, when we switch from monthly to yearly or vice versa in mobile, the user doesn't get to know what exactly changes because there is no movement or update on the screen. I'm attaching a video for reference.
I feel we should scroll the user to the pricing section (where the amount is changed) if they switch between the monthly/yearly tabs.
Screen.Recording.2024-02-01.at.12.24.08.AM.mov
Additional Information & Alternatives (optional)
No response
Do you want to work on this improvement?
Yes
Please check the boxes that apply to this improvement suggestion.
The text was updated successfully, but these errors were encountered: