HTML Form eSignature Workflow for Mobile-Responsive Certification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current E-signature interfaces lack the capability to receive signatures in a responsive fashion, particularly on mobile devices, as they are traditionally performed on PDF documents that are rasterized images, which are not mobile-friendly and do not allow for pinch-zoom capabilities.
Innovation Solution
An eSignature platform that retrieves HTML-formatted documents, applies data capture and signing rules, converts them to PDF, receives signatures on the HTML format, and applies these inputs to the PDF format, ensuring compatibility and responsiveness across various devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If E-signatures are performed on PDF documents (rasterized images), then document certification is achieved, but mobile responsiveness and pinch-zoom capabilities are lost
Solution Approach 1:
The system segments the document delivery process into two distinct formats: HTML for the signing interface (providing mobile responsiveness) and PDF for the final certified document (providing reliability). This segmentation allows each format to serve its optimal function without compromise.
Solution Approach 2:
The system introduces an intermediary conversion process that transforms the signed HTML document into a PDF format. This intermediary step preserves the mobile-friendly signing experience while delivering the reliable, certifiable PDF output required for document certification.
2Reliability
If E-signatures are performed on PDF documents (rasterized images), then document certification is achieved, but pinch-zoom capabilities are lost
Solution Approach 1:
The system segments the document format usage by function: HTML format is used for the signing interface where adaptability and pinch-zoom capabilities are needed, while PDF format is used for the final certified document where reliability is paramount. This functional segmentation resolves the contradiction between certification reliability and zoom adaptability.
Solution Approach 2:
The system changes the format parameter of the document based on the operational phase: HTML format (with adaptability and zoom capabilities) is used during the signing phase, while PDF format (with certification reliability) is used for the final output phase.
3Device complexity
If traditional E-signature interfaces are used, then simplicity is maintained, but mobile device compatibility is reduced
Solution Approach 1:
The system segments the interface delivery by device type and function, serving HTML-based interfaces for mobile devices (enhancing compatibility) while maintaining simple, familiar interfaces for desktop devices. This segmentation allows mobile compatibility improvement without unnecessarily complicating the overall system.
Solution Approach 2:
The system implements a universal platform that can deliver appropriate interfaces across multiple device types. The HTML-based signing interface serves as a universal solution that works across mobile devices, tablets, and desktops, providing both simplicity and broad compatibility.
Data Source
AI summary
Systems and methods for electronically signing HTML forms including retrieving a HTML-formatted document; assigning data capture and signing rules to the HTML-formatted document; converting the HTML-formatted document to a PDF-formatted document. transmitting a signature request to sign the HTML-formatted document; receiving a signature input on the HTML-formatted document; applying the signature input to the PDF-formatted document; and transmitting the PDF-formatted document.