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
UX improvement during Sign Up #1136
Comments
Thank you for opening your first issue and for being a part of the open signing revolution! |
Would like to work on this feature, if approved. |
Hey @cchirag! This is a feature we have been researching in our backlog for a while to improve the signature workflow for all places where signatures are required. There are some considerations we are waiting on, such as:
Since we're still researching this, our desired outcome might end up being different to yours, which will mean we can't guarantee merging your solution. If you want, you can work on this issue and we will review it to see if it fits our purposes. |
Thanks @dguyen . Will keep you guys posted |
Screen.Recording.2024-05-07.at.5.44.51.PM.movHey @dguyen,
There are many things that needs to be refined here, like:
Please feel free to share your thoughts so that I can continue with improving or changing things wherever necessary. |
Hello! Are you using a custom server for socket.io? If so I don't think Vercel supports that |
Ohh okay. I was trying a different approach with trpc subscriptions. Let me check and get back. |
Hey @dguyen, |
Thanks for looking into that! We're very against being vendor locked for features so I think websockets are out Have you had a look at WebRTC? That was probably going to be our choice of communication method between devices Also just a note in your demo, you have the devices bi communicate on the signature canvas whereas we only really want the mobile device to be able to modify the canvas, if that makes sense Edit |
Hey, just went through WebRTC's implementation and I don't think it can help us achieve the feature we are looking for. |
I don't think you need sockets or signaling https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Session_lifetime#signaling
|
Hey @dguyen, I did few experiments with WebRTC using socket and fetch. Sockets are out of options since we cannot have an open connection in a serverless environment.
I am really sceptical with respect to the use of WebRTC for this specific use case. Maybe we can refine this a little more and come up with something. Sorry for the constant back and forth. |
Hey @dguyen, any updates? |
Sorry I don't currently have time to deeply look into this so I don't have much suggestions at the moment |
Feature Description
During the Sign Up process, the user has to input his/her signature. The experience of trying to sign in a place using mouse or trackpad is bad and the result might be inaccurate. The feature might be to let the user shift to a mobile device (mostly touch screen these days) for making the initial signature without loosing the context in the desktop.
Use Case
Use case is when a user has to sign up to the app using his/her desktop or laptop. I faced this issue while registering myself and quickly understood that the UX could be improved.
Proposed Solution
Proposed solution is:
Alternatives (optional)
No response
Additional Context
No response
Please check the boxes that apply to this feature request.
The text was updated successfully, but these errors were encountered: