-
-
Notifications
You must be signed in to change notification settings - Fork 121
[FEATURE] Better user #/signin flow #140
Comments
I can work on it once PR #133 is merged. |
Alright now that #133 is merged. I'll start working on this one. My plan is to do the following:
I'll send a series of PRs. |
Hello @subhoghoshX @ykdojo Can we improve the UX of Sign-up by removing text fields and including "# with google", "# with Twitter", or "# with GitHub", this helps in completing the # process easier for the users to #? |
Could you elaborate on what you mean by removing the text fields? And I think PR #114 is working on adding social authentications. |
Oh, I'm saying instead of giving an option to the user to fill in the username or mail and password. We can have social authentications for sign-in and sign-up. If a user tries to # with an unregistered google account/Apple account/Twitter/Github then
If a user signs in with a registered google account/Twitter/Github/Apple account then
|
Got it. Thanks. As I mentioned social authentication is already in progress. And I believe we should have both options (social & email/password) as some users prefer email/password login. |
Hi @subhoghoshX you can check out the user flow here to see if it corresponds with your idea on the sign-up flow: https://www.figma.com/file/DtaNEDhDNz0Wgs4XohV6Pt/Defaang-User-Flow?node-id=0%3A1 |
Already checked it. Thanks for the amazing work @yaa-chi. |
You're welcome @subhoghoshX . There's more to come!🥳🎉 |
Hey @subhoghoshX , @ykdojo UX experience can be improved when user presses signin or # button. There should be a loading animation on the button or all over the screen. What do you think? |
Sounds good. I don't see many sites using it though. Open to discussion. |
I think the idea is that this process should be fast enough, a loading screen won't make sense - but open to discussion, too |
I don't think there's a need to have that either. We can have the loading screen somewhere else though👌🏾 |
@subhoghoshX Just saw it, thanksss |
Description
We should handle user #s & signins better.
There are many things to do there:
Better error handling, clearly showing that users have signed in (related to #122), etc.
The text was updated successfully, but these errors were encountered: