With this beta, you can add a Signature Input and start creating custom forms that your visitors can sign.
To access this feature, visit your partner dashboard or click here to be redirected there.
Go ahead then! Put in that final missing piece in those Application Forms, Incident Reports or Health Declarations. As always, please leave your feedback for @eyalc and our product team below.
Yea! This is Dope!
This is very cool!
Thanks Steven!
So here’s what you need to know:
To get your hands on a Signature Input you first need to turn on Dev Mode . Then head over to the Add Panel where you will find it under the Input section.
Here is the Corvid API Documentation of $w.SignatureInput . In particular I recommend you read the Introduction section which explains how to store an image of the signature in a Data Collection. The “Get a signature input and insert it in a collection” code example next to the documentation of .value may come in handy as well.
There is also this demo which we intend to turn into a full-blown Corvid Example soon.
Update: This is now fixed. Mind that code completion in the Corvid IDE may not work for some of you yet. However, even if your IDE shows validation errors for your code, it should run and work just fine. Also, the Properties Panel may not reflect to correct event handlers yet. All this should be fixed soon.
Your feedback is highly appreciated!
Enjoy 
Amazing Eyal! Is this open for languages?
Awesome
Yes, this is available (to Beta Partners) in all languages.
Thats really cool
This is great! My clients really need this feature
Very cool right?
Any feedback on Signature Input? What is it like to use it?
Share your website perhaps?
Thanks!
Hi Eyal, a question that came up within the Facebook group was if these were printable?
@eyal @eyalc Hello. Greetings of the day. This feature is really neat. Here is my constructive feedback-
Can this Image or feature directly, be connected/ integrated with third party appications such as DocuSign etc?
I’m more of a designer, and as a designer what I see is totally a different use for this feature. Instead of using this feature for signs, one can also use for websites which requires Doodling or Sketching, or simply Annoting. To extend the same feature for different use cases, such as the one I just mentioned, if you can have an option to “Change color/s” of the Pen, which can be controlled by the user i.e. fontend, maybe 3-4 basic brush/ pen types. That is it, and this can become an amazing canvas using which people can Create websites or webapps like autodesk sketchup. Just an idea to extend the use cases of this feature.
Great job nonetheless.
Thanks @stevenjose ! Tried reaching out to her, to no avail.
If you keep an image of the signature in a Data Collection, you can download it to your device then print it like any other image.
To download the image of the signature, open the Data Collection it is stored in, click the action menu (the three dots button) next to the signature, and select Download.
Thanks @stevenjose ! Tried reaching out to her, to no avail.
You can print an image of a signature stored in a Data Collection by first downloading it to your device. Then you can print it like any other image.
To download an image of the signature, open the Data Collection it is stored in, click the action menu (the three dots icon) next to the signature, and select Download.
Obtaining a printable version of a filled-in form is not currently supported as far as I know. However, once we add a Connect to Data panel to Signature Input (in plan for the current quarter) it could be achieved by building a page for site admins with the same form connected to a read-only dataset (connector). This will populate the form with the submitted data and let the user print it using the browser’s built-in printing functionality.
HTH
@developershreyan Thank you very much for your excellent feedback!
I am tempted to say “Yes”, but then I guess it depends on the exact type of integration you have in mind. Could you please tell us more about your use case?
This is a great point to bring up. One of the first decisions we had to make when we started with this product was whether it should be targeted at use cases specific to signatures (e.g. contracts), or at more generic ones (serve as a free canvas). We concluded that the requirements for the two products are quite different, both from the perspective of the site visitor and from that of the Wix Editor user. Since demand for a signature input far surpassed that of a free canvas, we decided to go with the first. You are very welcome to request this feature and have others vote on it.
You gave one good example of a feature that is needed for one product but not so much for the other, and there are quite a few other such features. In addition, to give you a taste of other considerations we take into account, we look at things such as: the experience of blind users who require assistive-technology to read out loud the content of the webpage to them (reaching a signature field that identifies as free canvas can be very confusing), how effective our help articles would be for the majority of use cases (in this case, signatures) if we used broad terminology, and legal considerations involved in one product but not the other.
Thanks again for the great feedback!
If only it was available on editorx 
Hey @patrick , thanks for the feedback!
I let the Editor X team know that you are interested in using Signature Input.
Adding elements to Editor X sometimes requires making necessary adaptations. For this reason, the team typically adds popular elements before less commonly used ones. If you tell your friends and family about Signature Input it might help 
Can you also let them know I would like to have the address input on editorx as well? Thanks!
Just did. Thanks!