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. It synthesizes masking noise on the phone, sample by sample, keeps playing after a call, an alarm or a headphone disconnect, and shows a log of the night each morning. A PHP server we wrote checks the one-time purchase a second time against Apple's signature.
Many people fall asleep to background noise. When a call, an alarm or a dropped AirPods connection cuts it off during the night, they find out in the morning, and nothing tells them when or why it went quiet.
We built Nightproof as our own product and made all-night playback its core promise, with a PHP server beside it that checks each purchase against Apple’s signature. The English-language app, with the US as its base market, is now in App Store review.
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.
Seven textures, from white noise to a fan rumble, come out of separate filter chains. A test hashes buffers and fails on any repeated block.
Calls, alarms, route changes, media-services resets and engine reconfiguration land in one supervisor. When headphones drop, a setting decides between the speaker and a pause.
The clock is passed in and audio hardware sits behind a protocol, so interruptions, route changes and stalls run in tests with no iPhone attached.
Each night goes into SwiftData as a stream of fifteen event kinds. Played time sums only played segments, so gaps never count.
It accepts only chains ending in Apple Root CA G3, matched by SHA-256, judges validity at the signing date and refuses Xcode transactions.
A refund notice from Apple or a server rejection withdraws Lifetime access. A server outage does not: StoreKit's own check keeps it open.
| Challenge | Result |
|---|---|
| A looped recording jumps back to the same point each time it reaches the end | The phone computes every sample in code; the app carries no audio file at all |
| A call, an alarm or a headphone disconnect cuts in and stops the sound | Sound returns once an interruption ends and moves to the iPhone speaker if headphones drop |
| The audio engine can stall with no reason from iOS, and that silence leaves no trace | A stalled engine gets up to three restarts; failing that, the log notes when sound stopped |
| PHP has no official App Store Server Library, so the server checks Apple's signature itself | The server pins Apple's root certificate, and a refund notice withdraws Lifetime access |
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.
Nightproof is in App Store review and cannot be downloaded until Apple signs it off. You can send us your question about it.
