Apps
A field record that can leave the phone.
Designing the handoff, not just the screen.
By Jay Fan · · Product notes / browser sample
An app used on site needs to help someone finish a job with limited time and attention. For a record-making workflow, the outcome is not merely a completed form: it is a document that someone else can read and understand.
The workflow
- Describe: Capture the change and its scope.
- Record: Keep the relevant evidence together.
- Review: Check what will be handed over.
- Export: Create a readable record.
Design around a small finished action
Change Order Proof focuses on a construction change record with scope, jobsite photos, signatures and PDF sharing. AutoProof applies a related evidence-and-handoff idea to vehicle before-and-after records. They are separate products and should not be presented as one generic app with different colours.
Show the outcome before asking for trust
The portfolio includes an editable browser walkthrough: enter a scope and amount, review the values and download a sample PDF. It is intentionally smaller than the iPhone product. There is no pretend signature, customer record or background save.
Make the review meaningful
A review screen should reflect the current inputs rather than repeat a static success message. A person should be able to go back, correct a value and see the export change with it. In a real deployment, offline behaviour, device access and document storage need separate acceptance checks.
Carry the pattern into another business
The reusable idea is a focused mobile workflow with a clear recipient and output. Inspection records, service visits and handovers may be candidates, but each requires its own fields, evidence requirements and validation with people doing the work. The right first version completes one useful task end to end.
Let the person inspect the record they are about to share.
Scope & status
The browser sample is unsigned and saves nothing. Product release labels remain separate: Change Order Proof has an App Store link; AutoProof is presented as an internal TestFlight beta.
The interactive examples are available with JavaScript enabled.
Discuss a project with JayKeep exploring
Business systems
The website is only the beginning.
A website opens the conversation. A CRM gives that conversation an owner, a history and a next step.
Specialist software
A roof becomes a working design.
Inside a solar-design prototype: real module dimensions, editable arrays and a proposal that keeps its assumptions attached.