Hey everyone — Chris here, founder of Actually Done.
I want to share the real story of how this app came together, because I think it's relevant to a lot of people in this community who are sitting on an idea but don't think they have the "technical" skills to build it.
The problem started small. I had passwords scattered across three different places. Medical records I could never find when I actually needed them — at the doctor's office, filling out a form, dealing with an insurance call. A running mental list of "life admin" tasks I kept telling myself I'd get to eventually. None of it was urgent enough to fix on its own, but all of it added up to a low-grade kind of chaos I was tired of carrying around.
So I built the thing I wished existed. One place for documents, budgets, medical records, passwords, and all the scattered pieces of life admin that never seem to have a home.
Here's the part that might be useful to some of you: I have no formal coding background. I built this entirely on my iPhone, using Replit's AI agent as my build partner. That meant learning a completely different way of working — I couldn't just write code myself, so I had to get really disciplined about specs, QA, and catching problems before they shipped. I treated every feature like a small project: write clear instructions, test it thoroughly, batch bug fixes instead of chasing them one at a time, and never trust "it's fixed" without actual proof.
That process ended up teaching me as much about product thinking as it did about building. I did a full pass through every section of the app — dozens of them — testing as a brand-new user would, and fixed everything from small UX issues (auto-capitalization, dropdown fields that didn't accept custom text) to more serious ones (a file upload bug that was silently rejecting real phone photos, a database issue that was dropping transaction records). Finding and fixing root causes rather than patching symptoms became the whole game.
Today the app covers passwords (zero-knowledge encrypted), medical records with an emergency card feature, budgeting, document storage, and a handful of smaller tools that solve the "I'll deal with it later" problem across different parts of life. It's live now, and I'm bringing it to Product Hunt on July 21.
If you're an aspiring founder who assumes you need to know how to code before you can build something real — I'd push back on that a little. The tools have changed a lot. What matters more is being rigorous about what "done" actually means, testing relentlessly, and being willing to be your own hardest critic.
Happy to answer questions about the build process, working with AI coding agents, or anything else. And genuinely curious: what's the one piece of "life admin" you keep meaning to deal with but never actually do?