Deductify ships its own iOS products, engineers IoT and connected-device systems for clients, and is building Doseline — medication adherence software for care teams.
We build our own products because it keeps us honest about the work we do for clients — the same constraints, the same App Store review, the same support inbox.
On the App Store
Habit & goal tracker
Measurable daily goals, progress statistics, and mood tracking — with every entry stored locally on the device. Ships with an Apple Watch app, widgets, and Live Activities.
On the App Store
Plant identifier & care
Identify a plant from a photo in seconds, then get care guidance for that species — watering intervals, light requirements, and seasonal notes, with your collection in one place.
Medication adherence · B2B
A shared record of what a patient was prescribed and what they actually took. Clinicians set the regimen, patients confirm doses, and care teams see adherence before the next appointment instead of guessing at it.
Connected hardware usually fails on the software seam — the pairing flow, the sync that breaks in a basement, the dashboard nobody can read. That seam is the work we take on.
iOS companion apps for Bluetooth LE, Matter, and Thread hardware — pairing, control, state sync, and the recovery paths for when a device drops off the network.
Protocol and payload design across the hardware boundary, provisioning flows, and over-the-air update delivery that survives real-world connections.
HomeKit and Matter accessory integration, Apple Watch companions, widgets, Live Activities, and background execution that actually works within iOS limits.
Local-first data models, queued commands, and conflict resolution — so the product behaves predictably when connectivity is intermittent rather than assumed.
Device data ingestion, time-series storage, and operator views that answer the questions your support and ops teams actually ask.
Credential and key handling on-device, secure provisioning, and setup flows measured by how many users complete them, not how many features they expose.
You talk to the people writing the code. Every engagement runs the same four phases, and you can stop after any one of them.
A paid discovery week. We map the hardware, the constraints, and the unknowns, and hand back a written technical plan you own outright.
The riskiest piece gets built first — usually the connection layer. If something can't work, we find out in week three rather than month five.
Two-week cycles with a working build at the end of each. You see progress on a device, not in a status document.
App Store submission, documentation, and a handover your own team can pick up. We stay on for support if you want it, not because you're locked in.
Tell us what you're building and what's in the way. If we're not the right fit we'll say so, and usually point you somewhere better.