The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
Our own iPhone app for small trade businesses. A painter or handyman pairs a before photo and an after photo with a note for each task, and the app lays them out as a PDF carrying the business logo and license line. Everything happens on the phone: no account, no server, no network calls.
A gutter cleaner finishes the job, and the proof is scattered across the camera roll and a text thread. Months later the client says the stain was already there. Nothing on hand ties those photos to a job or a date.
We built ProofPair as our own product for solo tradespeople and small crews in the US, UK, Canada and Australia. The app is in English. The hard part was the document: notes that never get cut off, photos stripped of location, all produced on the phone.
We go through how the work runs today and what you expect from the software; the scope comes out of that.
We decide what the system is made of and where its information is kept.
We draw the screens and the flow before any code, and start building once you have approved them.
We write and hand over the software so another team could carry it on.
A planning pass decides what lands on each page before anything is drawn. Notes flow through TextKit, one text container per page's remaining height.
Reports use Helvetica: the system font lost Unicode mapping for some glyphs and broke search. The same input yields the same page layout.
One versioned JSON file holds everything. Each write backs up the last valid copy first; files from a newer app version stay untouched.
Pre-release checks fail if network APIs or unlisted imports appear. The first job's report is free; a one-time Pro purchase opens the rest.
| Challenge | Result |
|---|---|
| A long task note hits the bottom of the page and gets clipped in the PDF | Overflow carries onto the next page; each before and after block stays on one page |
| Phone photos carry GPS and camera metadata, and their capture date is not always known | Photos are re-encoded on import without location data; reports label dates 'Taken' or 'Added' |
| One interrupted save or a corrupted file could wipe months of job history | Saves are atomic; an unreadable file is quarantined and the last good backup loads |
| A one-time purchase stored as a local flag can outlive a refund | Pro access is recomputed from StoreKit-verified transactions; refunds and revocations take it back |
Our own workshop software, built around the car on the ramp. A work order, the parts it consumes and the invoice it produces run as one chain, and the accounting side hangs off that same record. Maintenance history lives on the plate and chassis, so it travels with the car.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
Our own product, still in development and not yet live. How long an appointment runs, what it is booked against and how bookings stack all differ by trade, so we are keeping those rules configurable inside the product instead of fixing them in code.
ProofPair is in App Store review and cannot be downloaded until Apple signs it off. You can send us your question about it.
