I designed and engineered ehllo, a digital business card with a private memory of everyone you meet, from first commit to Google Play in about ten weeks. I was the only person on it. I worked with AI as my engineering, QA and release team, and I made every product and design decision myself.
You meet someone at an event. You swap details, talk for ten minutes, promise to send them an intro. A week later you can't remember their surname, the event, or what you promised. ehllo is built for that gap. You scan or share a card, capture the conversation, and ehllo remembers who they are, where you met, what you talked about and what you promised. Then you can ask it anything, typed or out loud.
The harder story sits underneath. A product this size usually needs a team: mobile, web, backend, AI, QA, release. I had none of those people. So the real design problem was twofold. What should ehllo be, and how does one person ship and run something this complex without breaking people's data?
Product design Mobile and web AI product Solo founder-designer
Memory first on the phone, the public card on the web: one product, two ways in.
| Product | ehllo: a digital card plus relationship memory |
|---|---|
| Role | Founder, product designer, engineer |
| I owned | Product, brand, UI, motion, architecture, every release |
| Team | Me, with Claude Code, Cursor and ChatGPT |
| Users | People who meet people: consultants, freelancers, founders |
| Platforms | iOS, Android, web, public card pages |
| Timeline | 25 Jul 2026 → Google Play 27 Sep 2026 (about 11 weeks) |
| Status | Live on Google Play · iOS in review · pre-revenue |
The first target was independent consultants, which I logged as an unvalidated hypothesis. Real testers started on 8 October 2026, and iOS testers are on TestFlight.
Every feature serves one of three jobs, and each screen gets one dominant job.
People meet constantly, at events, on calls and over coffee, and they lose the thread. Names, context, promises and follow-ups all slip. Business cards end up in drawers. CRMs are built for sales teams and expect data entry. Note apps don't know who anyone is.
The insight I built on: the moment you meet someone is the moment to capture the relationship. If capture happens there, in seconds, an assistant that sees all of it can answer the questions people actually have: "How do I know her?", "What did I promise him?", "Who was at that event?"
A re-scan opens "You've met before" on both phones. Both see the same date, and only Chloe's side shows what she remembered, because notes stay private.
One side of the scan
The other side