Improve fidelity between the Editor, Signer page, and final signed document.In October 2018 I was in a meeting where we were asked to bring ideas to: So at a minimum all fields need an address, width, height, type, and unique identifier. All three components-the Editor, Signer, and completed document-must display accurately regardless of the user’s screen resolution. This overlay process draws the fields over a transparent background (instead of the page image itself), which we merge with the original file to present onscreen. In both the Editor and Signer steps of the process, we show you images of your document’s pages and draw the signing fields on top of them. To make HelloSign work in any browser, we convert the document file that you upload to a set of images. Otherwise, users at both ends may not trust the system as much as they would handwritten ink on paper.īrowsers can’t display all the file types we support for signing. The three modes in which a document is presented-the Editor, the Signer app, and the final overlay as a single, immutable record for posterity-must each display their contents onscreen in pixel-perfect layout at each step, regardless of who’s looking at them on what. It’s trickier than it might seem to maintain pixel-perfect layouts for a wide range of document types and annotation fields across an ever-expanding range of screens. When they’re done signing, everything is reassembled into a PDF with signatures that serves as the legally-binding document. You send this prepared form to the recipient. HelloSign is a Dropbox company that provides a Web-based eSignature solution: If you have a document you want someone to sign, you upload the document file, then show you an editor in which you place all the fields to build the form the recipient will fill out-signatures, dates, initials, etc.

React dropbox api