My Notes Kept Vanishing, So I Had an AI Build Me an Inbox

I'm good at writing things down. The problem is finding them again. Receipts in the camera roll, ideas in chat, links somewhere. Two months later it ends in "where did I write that?" This is how a non-developer had an AI fix it — the parts that worked and the parts where I fell over.

1. My First Sentence to the AI

No grand spec. I just said: "When I send a memo or photo by chat, save it. If it's a photo, read the text and save that. Later, when I ask 'what was that ticket number,' find it."

The AI split this into a few functions: save, search, view, list. I didn't need to know what those were — just "yeah, do that." That's the good part of vibe coding: even without knowing the design, I say what I want and the AI proposes the structure.

2. The Key Turned Out to Be 'Store It in Two Places'

In my own words, here's what the AI explained: storing in only one place is risky. So we'd put each memo in two places.

• A search store — for finding fast. Type "ticket reservation" and related memos pop up.
• A plain-text vault — so that even if I stop using this tool someday, my notes remain as plain text files. Not held hostage by any one app.

I asked, "why save twice?" The answer: one to find fast, one to never lose. That line stuck with me oddly long. Even a non-developer got it.

3. In Practice — an E-ticket Came Back to Life

While prepping a trip I got a flight e-ticket. I just sent the screen to my AI assistant. It read the text (reservation number, flight, dates) and dropped it into the inbox. Days later I asked "what was that ticket number?" and got it back in one line. Before, I'd have scrolled the camera roll hunting for it.

4. And Here I Learned Something — 'Don't Hand Over All the Power'

To read notes across devices, they must sync somewhere. At first I thought, "just let the AI assistant do everything, right?" The AI pushed back. Give the assistant the power to do anything and it eventually comes back as an accident.

So we split the roles. The assistant only calls 'save'; the actually-sensitive work (pushing to other devices) is handled behind it by a separate part with limited privileges. That's how I first understood 'privilege separation' in my gut. Convenient and safe often point in opposite directions.

5. Lessons a Non-Developer Took Away

• Don't mistake the problem for 'not enough apps.' What I lacked wasn't a new app but 'one entrance' and 'one search.'
• Keep your data as plain text too. Tools change eventually. Text files don't betray you.
• Don't give the AI full power for convenience. Only what's needed, exactly that much.

6. FAQ

• Q: Why not just use a notes app?
  A: You can. But I needed 'save right in the conversation' and 'read a photo and search it.' The moment that worked, I stopped losing notes.
• Q: Can you build this knowing zero code?
  A: I don't know code either. Describe what you want; when it fails, paste the error as-is. But always ask 'why did you do it this way' — when it breaks later, that's your map.
• Q: The single most important thing?
  A: Storing in two places. One to find fast, one to never lose.

7. Closing

Personal knowledge management was a re-discovery problem, not a better-storage one. Funnel the entrance into one place, put a copy where it's fast to find and where it'll last forever, and the "where did I write that?" of two months later ends in a one-line search. I couldn't write the code, but I could make that call. That's the real fun of vibe coding.