I find a lot of scriptures during study. I underline them, save them, and tell myself I'll memorize them. Then I forget.
That loop bothered me. So I built Memr—an app that surfaces the verses I save everywhere I already spend my time: in the browser, in email, and soon on my phone.
The problem: save now, forget later
I'd come across a verse that landed. I'd jot it down or screenshot it. Then life would move on, and that verse would disappear into a folder or a note I never reopened.
Memorization doesn't happen from a one-time save. It happens from repetition in context—seeing the verse when you're not expecting it, when you're not "in study mode." That's what Memr is built for.
The browser is my home base
As a software developer and designer, I open a lot of tabs. The browser is where I work, learn, and read. So I built Memr to live there first.
The Chrome extension shows me the verses I've saved right in my tabs. Every new tab becomes a chance to see a verse again—and to actually remember it. I've had it set up locally for a while now, and publishing it to the Chrome Web Store is the last step I'm working through.
Beyond the extension, I've added email reminders so verses can show up in my inbox. A mobile app is in progress. The goal is simple: verses follow me wherever I am.
Why Firebase?
Memr doesn't need a sprawling backend. It's a focused app: save verses, sync them across devices, display them where they matter. Firebase handles auth, Firestore, and real-time sync cleanly, and it scales well—especially for the mobile app I'm building.
It keeps the architecture simple so I can spend more time on the product and less on infrastructure.
A path into mobile
Memr is also my entry point into mobile development. I've been building for the web for years; mobile is the next frontier. Building something I actually use every day—an app that surfaces scripture in my tabs and pocket—gives me a real reason to ship and iterate.
If you've ever saved a verse and then forgotten it, Memr is built for that. The Chrome extension will be out soon. Until then, I'm using it locally and refining it—one tab at a time.
