Begin with the file.
The first screen gives the document upload area most of the page. It makes the next action obvious and keeps the interface from asking the user to understand a tool before there is a document to work on.
QSign · Independent Project
A small signing tool for the moments when a document just needs a signature.
QSign is a browser-based tool for placing a custom signature on a document and exporting a PDF. I designed and built it around a short path: choose a file, add a signature, place it, then export. The live product keeps document data on the device.
Problem
Signing a file is often a one-off task, not a project someone wants to set up.
QSign starts with the file instead of a dashboard. Its entry state accepts PDF, JPG/JPEG, and HEIF files, then directs the task toward adding a signature and exporting a PDF. The live site also states that document data stays on the device, which matters when the file is not something a person wants to hand to another service.
Workflow
Four steps, with the document at the center.
QSign asks for four actions: choose a document, add a signature, place it, and export it. The sequence stays close to the signing task rather than expanding into a general editing workspace.
- 01Choose a document
- 02Add a signature
- 03Place it on the page
- 04Export a PDF
My Role
I built the working browser tool, not just the interface.
QSign is an independent project. I designed the interface and interaction flow, then implemented the browser-based product. The work includes the PDF.js document workflow, signature placement, and the final PDF export path.
Key Decisions
Put local handling in the product explanation.
For a signing task, the document can be the sensitive part. QSign makes the claim that data stays on the device visible on the entry state, alongside the product's basic capability, rather than leaving it only to a policy page.
Keep placement separate from signature creation.
A signature and its position solve different problems. Separating them keeps the user from arranging a page while still deciding what the signature should look like.
Outcome
A live, focused workflow for signing and exporting a document in the browser.
QSign is live at qsign.cc. The current version accepts document and image inputs, supports custom signatures, and exports a PDF. I do not have a verified completion or adoption metric for this project, so I have not attached a performance claim to the release.
Reflection
There are still questions I would test with real signing sessions: where people hesitate between creating and placing a signature, how they handle multi-page files, and whether placement remains precise on smaller screens. I would test those basics before adding broader editing tools.
Next Case Study
Designing a mobile sports betting screen for a three-second read.
A timeboxed design challenge that removes 40 percent of the requested data to make one game state easier to scan.