Actually Done
The life-admin app that actually gets things done.
10 followers
The life-admin app that actually gets things done.
10 followers
Life admin, actually done.Actually Done replaces five different apps with one: bills, subscriptions, appointments, documents, and medical info in a single place. Highlights: client-side OCR scanning digitizes documents in seconds, a medical emergency card with a public QR code for first responders, zero-knowledge encrypted password vault, and pantry barcode scanning. Built solo, mobile-first, veteran-owned. Founder pricing: $9.99/mo for the first 100 users, locked for life.
Hey Product Hunt 👋
I'm Chris, a veteran and solo founder — I built Actually Done from a single question: what's the one app nobody's built yet that handles the boring-but-critical stuff in your life? Passwords, IDs, medications, important documents, the birthday you always forget — all scattered across ten different apps and a few sticky notes on the fridge.
Actually Done pulls all of it into one place, built for real life, not just to-do lists:
🔐 Zero-knowledge encrypted Password Vault — even we can't see your passwords
🆔 ID Vault with masked/reveal fields for sensitive documents
💊 Medication tracking with label scanning
🚨 Emergency Card with a QR code for first responders — works even if your phone is locked
📄 Document and credential scanning with auto-fill
📅 Expiring Soon dashboard so your passport doesn't sneak up on you
🔍 Full-app search across everything you've saved
💰 Budget Planner for the financial side of life admin
Who it's for: honestly, anyone who's tired of being the one person in their household who has to remember everything. Caregivers, parents, people managing aging parents' affairs, or just anyone who wants their life admin actually done instead of half-tracked across five apps.
For Product Hunt: use code PH30 for a 30-day free trial (no card required to start).
This is a solo build and I'm still learning what real users actually need versus what I assumed they'd need. I'd genuinely love your feedback — what's missing, what's confusing, what you'd want built next. Not asking for upvotes, just want to hear from people who've felt this exact headache.
(Fun fact: this whole app was built on a phone with an AI agent — no laptop, no formal coding background. Turns out "there's an app for that" now also applies to building the app for that.) 😄
Thanks for taking a look 🙏
the medical emergency card with the public QR is such a thoughtful detail, especially coming from a vet-owned build. love that the whole thing runs client-side too, feels like it actually respects the user instead of just saying it does.
@aselnorgaz93673 Thanks, Asel — that really means a lot, especially the "respects the user" part, since that was the whole design goal, not just marketing language.
Quick honest note since you mentioned client-side: the Password Vault is fully client-side encrypted (PBKDF2 + AES-256-GCM, we genuinely never see the plaintext). The Emergency Card QR works a little differently — it's a rate-limited, read-only public route with a 256-bit token, so it's accessible without login in an emergency but still locked down server-side. Wanted to be precise about that distinction since trust in the details is kind of the whole point of this app.
Appreciate you noticing the emergency card specifically — that one came from thinking about what actually matters if something happens to you and a stranger or EMT needs your info fast, without needing your phone unlocked or an app download. Glad it landed the way I hoped it would.
Congrats on shipping this solo from your phone. The emergency QR card is a nice piece of design, treating 'not everything belongs behind the vault's security model' as a real decision instead of an afterthought. On the household-sharing question below, are you leaning toward per-item re-encryption to each member's key, or a shared key wrapped separately per person?
@vollos Thanks — really appreciate that read on the QR card. For household sharing, leaning toward a shared key wrapped separately per member. Feels like the right foundation for scaling to more members without re-encrypting every item each time someone's added. Curious if that matches your experience.
@actuallydone That's the shape these key-wrapping schemes usually take for adds. Removal tends to be the tricky part: once someone's had access to that shared key, is it rotated and reissued to the remaining members, or does cutting them off just mean their API access stops while the older data sits under the same key?
@vollos Rotation, not just cutoff. On removal: a new shared key gets generated, existing items re-encrypted with it, and it's rewrapped for remaining members. Old key's wrapped copy for the removed member gets deleted. One caveat — if they had the vault open in a tab at that moment, they keep whatever's in memory until it closes. Same limitation 1Password/Bitwarden have.
@actuallydone Rotate-on-removal instead of just cutting API access closes the door instead of leaving old data reachable under the same key. And the open-tab caveat lining up with 1Password and Bitwarden's own limit means it's a shared constraint of the memory model, not a gap specific to this build.