Connected health device companion
The app beside a connected device: readings, context, and sharing that people actually use.
Device makers and care programs whose product is only as good as the companion app.
- Phone: today's readings with device status
- Web: thirty-day trend and care-team sharing
What goes wrong
without it.
A device that measures well still fails if pairing is fragile, readings arrive without context, and sharing a summary with a clinician takes screenshots and email.
What the product would do
- Pair and manage the device, including battery and firmware state.
- Show readings over time with the context needed to act on them.
- Share a summary with a clinician or caregiver, with consent controls the user understands.
- Prompt for missed readings; stay quiet when nothing needs attention.
- Export a dated report in a format a practice can file.
Decided before any screen
- What the data model owes to standards, so observations can reach care systems later without a rewrite.
- Which readings justify a prompt and which never should. Alert fatigue is a product decision, not a setting.
- Where consent, sharing, and revocation live, and how they are evidenced.
Specified once.
Built in parallel.
Well-bounded screens behind one strict data contract. The record and the sharing rules are specified once; the many views of them can be built in parallel and verified against the same acceptance criteria.
Want to see this in practice? Let’s discuss your use case and explore relevant products I’ve built.
Other problems, same approach.
Start with the problem,
not the proposal.
Talk with me about what you need to build, fix, or decide. We’ll explore how Phase 3 Services can help and what an engagement would involve.