> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# When to use the Android SDK

> Our Android SDK wraps the Docusign eSignature REST API functionality into a package that is optimized for mobile development.

The Android SDK wraps the [Docusign eSignature REST API](/docs/esign-rest-api) functionality into a package that is optimized for mobile development. The table below outlines the high-level differences in capabilities between the Android SDK and the eSignature REST API to help you determine which is right for your application or scenario.

| Feature                         | Android SDK                                                                                                                              | eSignature REST API                                                                       |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Core technology                 | Kotlin-based library with native Docusign UI components                                                                                  | Android developer access to Docusign eSignature REST API via language service layer       |
| Full eSignature REST API access | Yes, eSignature REST API access is supported                                                                                             | No, most API endpoints are covered, but no offline access or account management endpoints |
| Offline capabilities            | Yes, offline signing driven by templates and envelope creation                                                                           | No, online only                                                                           |
| Native signing UI components    | Yes, leverages native components such as native signing                                                                                  | No, developers must build custom UI components to support API requests and responses      |
| Supports all Docusign tab types | Agreement creation and offline signing supports signature, initials, name, date, textbox, checkbox, company, radio button and title tabs | Yes, all tab types are available and supported                                            |