SignArgs: PDF Rendering & Document Signing
smartargs
$43.45
$86.90
50%OFF
(no ratings)
Jump AssetStore
Show PDFs, capture handwritten signatures and sign documents on the device: signatures stamped, an audit page added and a hash-linked record anyone can check. No server needed.SignArgs puts document signing inside your Unity application. Show a PDF, let people sign it with a finger, pen or mouse, and finalize the signed document on the device: every signature stamped in its box, an audit page appended that says what was signed, by whom and how to check it, and a bundle of records written next to it. No server, no account for the signer, no network connection.A handwritten image pasted into a PDF proves little. SignArgs binds each signature to the pages rendered and shown: the exact bytes of the document, a hash of every page as it was drawn on screen, every input event of the stroke with its device timestamp, the consent sentence the signer agreed to, and whatever context your application binds to it. Every step is one link in a hash-linked audit chain.Show the document Pages render off the main thread with form field values drawn, onto a RawImage in your own UI. Read the form fields a page declares, signature boxes included, to place signatures where the document says.Capture the signature Touch, pen and mouse through the Input System, recorded at event rate rather than once per frame, with pen pressure where the device reports it. The ink draws as a smooth mesh and is stamped from the same points.Several signers, in order A small template says where each signature goes, which sentence each signer agrees to, how sure your application must be of them, and who signs first. Several people sign one document in turn on one device; if someone cannot sign, finalize what is signed and the audit page names the open fields.Evidence from your application Bind a checklist, a screenshot or a model version to one signature or to all of them. It is stored as reported by your application, with which application, version and device reported it.Proof that can be checked The signed PDF, the original, one record per signature, the strokes, the audit chain and a manifest of SHA-256 hashes, in plain files. The records are canonical JSON with published rules, so anyone can verify a bundle with a SHA-256 tool and no SignArgs code.Pseudonymous records Names and contact details stay out of the records, in one separate file per signer that you can delete on request without breaking a hash.Built for shipping PDFium, the PDF engine inside Chrome, prebuilt and pinned, with our own bindings. IL2CPP with managed stripping "High" is tested from the first build, and the package feeds its own link.xml to the linker. Full C# source included.Two samples "Show a PDF" is the ten-second check that the engine runs on your target. "Sign a document" is the product: three people sign a handover protocol on one device, guided step by step, and the signed file lands in your app's storage.Platforms Verified on an Android phone (IL2CPP, stripping High) and on a Windows player. The macOS binaries are included but have not been run yet; iOS 17 and newer is a preview, wired into the Xcode project by the package and not yet run on Apple hardware.What it does not do SignArgs produces simple electronic signatures: there is no certificate, no digital signature over the PDF and no trusted timestamp, and times are device times. The viewer shows pages; it has no zoom, search or text selection. Everything runs on one device, so a remote signer needs a server. A digital signature, trusted timestamps and remote signers are planned for SignArgs Cloud; XR controllers and hand tracking are planned for SignArgs Pro. The documentation lists every limit.Documentation: Introduction · SignArgs for Unity docs · smartargsUnity 6000.0 or newer; developed and tested on 6000.3. Built-in render pipeline tested; the components are uGUI and ship no shaders or materials.Platforms: Android arm64 and Windows x64 player verified; macOS (Apple silicon and Intel) binaries included, not yet run; iOS arm64 device and simulator as a preview, minimum iOS 17, not yet run on Apple hardware. No 32-bit, Linux or WebGL binaries.Scripting: IL2CPP and Mono. IL2CPP with managed stripping "High" verified on Android; the package supplies its own link.xml to the linker.Dependencies (installed with the package): Input System 1.18.0, Newtonsoft JSON 3.2.2, uGUI 2.0.0. The project's active input handling must include the Input System.Native code: PDFium 156.0.8066 (BSD-3-Clause), built by bblanchon/pdfium-binaries (MIT), pinned by SHA-256. All native calls run on one worker thread, off the main thread.Full C# source included, no precompiled managed DLLs. Public API documented with XML comments.Audit page font: Roboto 2.138 (Apache-2.0), embedded in each signed PDF, about 200 KB. Covers Latin, Latin Extended, Greek and Cyrillic; use your own TrueType font for other names. Right-to-left and Indic scripts are refused.Output per signed document: signed PDF, original PDF, template, signature and stroke records, evidence, audit chain (JSON Lines) and a manifest of SHA-256 hashes; one identity file per signer kept outside the bundle.No networking code: the package makes no network connections.Enabling a signature pad turns off the Input System's merging of redundant events for the run, so no pointer moves are dropped.Documentation included offline in SignArgs/Documentation (quick start, concepts, one guide per feature, bundle format and verification, platforms, limitations, API overview) and online at Introduction · SignArgs for Unity docs · smartargs. Third-party notices included.An AI coding assistant was used throughout development, under my direction and review.
