There is a very specific kind of frustration that only shows up on a Sunday evening. You sit down to write sermon notes, open your favorite productivity app, and realize it was never built for this. Notion is powerful. It can hold your entire life in neat little databases. But it does not know what a sermon outline looks like. It does not know that you want to link a verse to a note, then link that note to a prayer point, then come back to it three weeks later and still understand what you meant.That frustration is where Selah started.The Problem Was Bigger Than NotesI run an online prayer group with a small circle of Christians in tech. We are scattered across time zones and cities, but every week we try to gather anyway, mostly on WhatsApp. And every single time, the same ritual played out. Someone would say "Open your Bible to this verse," and then we would wait. Someone opens a physical Bible. Someone else fumbles for an app. Someone reads out loud while three other people try to follow along on a screen that is not built for group reading.It worked, technically. But it was clunky, and it broke the flow of what should have been a sacred, focused moment.There was a second layer to this too. Reading a verse is one thing. Understanding what it actually meant, in its original context, to the people it was first written for, is another. I found myself constantly searching for background, historical context, and meaning, then trying to explain it to the group in real time. There was no single place that connected the reading, the context, and the conversation.And on top of all that, I wanted a simple way to share what I was learning with fellow believers. Not a sermon. Not a lecture. Just a genuine "here is something that hit me this week" moment, shared with people who would actually care.I looked around for an app that did all of this. I could not find one. So I decided to build it myself.Building SelahSelah became the answer to three problems at once. A note-taking experience actually designed around sermons and scripture, not repurposed from a generic productivity tool. A shared space where a group could open the Bible together without the WhatsApp shuffle. And a way to actually understand what a passage meant, not just read it and move on.I built it the way most indie developers build things. Alone, mostly at night, testing ideas against my own frustration until something finally felt right.The First Wall: Google's 12 TestersBefore you can even think about real users, Google wants proof that real people have tested your app. 12 testers, to be exact, actively using it for two weeks before you can request production access.If you are not already sitting on an audience, this requirement quietly becomes one of the hardest parts of the entire launch. I did not have a waiting list. I did not have a following. What I had was family and friends, so I asked them, one by one, to install a rough version of an app and actually use it, not just open it once and forget.They came through. And with that, I crossed the first wall.The Rejection I Was Ready For, and the Approval I Was NotI braced myself for at least one rejection. Everyone who builds for the App Store or Play Store tells you the same thing. Expect pushback. Expect a policy you did not know existed. Expect to resubmit.Selah got approved on the first try.I remember staring at the notification for a moment, half expecting it to be a mistake. It was not. The app was live. People could actually download it now. After months of building in private, something I made was finally sitting in a public store, waiting for strangers to find it.The relief lasted less than a day.When Sign Up Just Stopped WorkingAlmost immediately after going live, new users could not sign up. Not slow, not buggy. Completely broken. Someone would try to create an account and it would simply fail, no clear error, no obvious clue.For two days I lived inside that bug. I checked my code line by line. I checked the database. I checked every setting I could think of, convinced the answer had to be something dramatic and technical.It was not.I run more than one project, and each one has its own account with Resend, the service that sends transactional emails like sign up confirmations. Somewhere along the way, I had wired Selah up with the API key from a completely different project, my Bible study app. The key was valid. It just did not belong to Selah. So every sign up email that should have gone out simply vanished into the wrong account, and new users were left staring at a screen that never confirmed anything.I found it, fixed it, and thought the worst was over.It was not.The Missing HyphenRight after that, a second issue surfaced. Users signing in with Google were being authenticated successfully, but then getting stuck on the website afterward. The login worked. The redirect did not.I went back through the Supabase configuration certain I would find something complicated. Instead I found this. My auth callback URL was supposed to read auth-callback. Somewhere in the setup, it had been entered as authcallback. One missing hyphen. That single character was enough to break the entire flow and strand every Google sign in on a dead end.I fixed it, tested it, watched a sign in actually complete for the first time in days, and felt something close to disbelief. Two separate outages, both caused by things so small they were almost invisible. A wrong key from another project. A missing hyphen. Nothing about either of them showed up in a stack trace pointing straight at the answer. Both took patience, and a willingness to question the parts of the system I assumed were already correct.Where Things Stand NowSign ups work. Google sign in works. The app that started as a personal frustration with sermon notes and a clunky prayer group routine is now live and functioning the way it was meant to.You can download it here https://play.google.com/store/apps/details?id=com.nanzing.selahRight now, we have two users on a free trial.Two might sound small. After everything it took to get here, from chasing down fourteen testers with nothing but personal favors, to an approval I did not expect, to two outages caused by mistakes hiding in plain sight- two feels like proof. Proof that the thing works. Proof that someone besides my prayer group and me finds enough value in it to actually try it.The current focus now is marketing, telling this story, and finding the people who have felt the same frustration I felt that Sunday evening when Notion could not give me what I needed for sermon notes, and WhatsApp could not give my prayer group a real shared space to open scripture together.If you have ever sat in a Bible study trying to follow along on a screen that was not built for it, or wished you understood the context behind a verse without stopping to search five different sites, that is exactly why Selah exists.We are just getting started. But we are live, we are working, and we are learning as we go, one hyphen at a time.