> For the complete documentation index, see [llms.txt](https://docs.shadowcipher.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadowcipher.in/changelog/2026/2026-11-13-mobile-signing.md).

# Mobile signing improvements

13 November 2026

Signing a PDF on a phone is now as easy as on a computer.

### Improved

* **Responsive signing page.** The PDF signing flow adapts to small screens.
* **Touch placement.** Signers can drag and place the signature placeholder with a finger.
* **Smoother scrolling.** PDF pages are no longer redrawn when only the screen height changes, such as when the phone's address bar hides or shows.
* **Responsive simulator.** The simulator layout works on phones and tablets.

### Developer tools

* Added a Postman workspace for the API.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadowcipher.in/changelog/2026/2026-11-13-mobile-signing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
