Contributed by Jon Shinault, Senior Developer at 

I was excited, perhaps anxious, when I was asked to take-on the project of adding eSignature functionality to’s iOS reference application. I am a novice iOS developer and the functionality seemed complex. My task: embed electronic signature sending and signing inside our existing iOS application. With the new DocuSign Mobile SDK, the work was simple and fast!! Here is how I went about it.

Looking at our existing app the proposed integration point was a no-brainer; allow our users to sign documents on any of our supported connectors, sign a contract in, or sign a permission slip for your child’s school in your personal Dropbox account.

First things first, I inspected our existing application to look for the perfect place to hook in the SDK. I will admit I went for some low hanging fruit out of the gate by taking the sample application that came with the SDK and modifying it for use in our applications. This provided our application with an extra, added bonus in my view, our app now would allow for users to sign ANY documents in their queue, not just ones initiated through The SDK and it’s examples gave our app a huge bonus right out of the gate and the implementation was easy to follow and integrate.

Now that the low hanging fruit was picked and I knew that the SDK was going to work swimmingly in our app, I moved onto the real meat of the integration. First step was figuring out where to initiate the signing action. I ended up moving some of our options to a swipe interface to allow for a more prominent signing choice. 

Now the Document link and Delete feature would reside on the file listing view with an iOS mail swipe interface. Even without the integration in place, the SDK was helping our application in the user interface category. The main selection action in our app is a preview of the file using a web view, I replaced the old “share” icon with a “signing” icon, a nice pen graphic J, and this was where the integration fully begins. The first thing in the flow I needed to do was to grab a copy of the file that needed to be signed. With’s APIdoc API this was very easy. With the DocuSign SDK there are easy to implement methods for envelope creation. With one line I handed over control of the app to the SDK and it handled everything from creation of the envelope to the actual signing process.  

Once the document is signed I added a prompt with a field where the user could select to upload the document back to their account with the option to rename if needed. If the user chose to upload the doc, I take advantage of the SDK and download a signed PDF version of the signed file. Using the APIdoc API, I placed the file back into the source storage (Dropbox, Salesforce, Sharepoint, etc.) via the account. The main integration was done and in place. 

As a developer with an important task and a tight timeframe, I found the DocuSign Mobile SDK and the Beta Heroes program to be invaluable. Within a very tight timeframe I was able to extend our app’s functionality by leaps and bounds with DocuSign. Now that phase one is done, I am already salivating over the features I could leverage for our users. 

Click here to learn more about how you can integrate eSignature and Digital Transaction Management services into your mobile apps with the DocuSign Mobile SDK.