9
14 Comments

How I survived 14 days in "Google Purgatory" as a solo Vibe Coder

Hey IH! I’m a solo founder and a proud "Vibe Coder." I don't spend years mastering syntax; I use AI (Gemini + Antigravity) to bridge the gap between an idea and a working product. I just cleared the biggest hurdle for indie Android devs: 14-day closed testing rule.

I built Keept because I’m obsessed with killing "Administrative Debt." You know, that mental weight of unfiled receipts, foreign invoices, and messy spreadsheets that keeps you from actually growing your business. But before I could save others, I had to save myself from Google’s bureaucracy.

Finding 20 reliable humans to test your app for two weeks straight with $0 budget is a nightmare. I turned to communities like App Hive and Reddit. It wasn’t just about getting the "tick" from Google; it was a crash course in:

  • Reciprocity: You test mine, I test yours. Community is the only way for solo devs to survive now.

  • Brutal Feedback: Other devs pointed out UI flaws I was too close to see. I added ZAR and INR support specifically because of beta feedback.

  • Validation: I realized "Administrative Debt" is a pain point everyone in the indie space feels.

Keept is finally LIVE on the Play Store. I'm currently running some Reddit Ad experiments (sharing insights on that soon!), but my main focus is now building in public here.

How are you navigating the new Google Play requirements? Does the "14-day rule" discourage you from launching on Android, or do you think it actually helps by filtering out low-quality apps?

Would love to chat and share notes!

👇 See it in the Google Play Store: https://play.google.com/store/apps/details?id=com.veritas.keept

posted toAvatar for product Keept
Keept
  1. 1

    The 14-day closed testing thing is genuinely one of the most underrated barriers for solo Android devs. Most people outside the ecosystem have no idea it exists, and finding 20 real humans who will actually stick around for two weeks is way harder than it sounds on paper.

    The reciprocity angle is interesting. That feels like a product in itself honestly. Some kind of matchmaking layer for indie devs who need testers and are willing to trade time. The fact that you had to cobble it together across Reddit and App Hive manually says something about the gap there.

    Curious how the Reddit ads are performing for something like receipt management. That feels like a tough category to target with paid because the intent is so diffuse. People don't usually search for a solution to administrative debt until tax season hits and they're already drowning. Would love to hear what you're learning there.

  2. 1

    I've heard many devs talking about that, it seems to be a real nightmare. And what about IOS?

  3. 1

    went through this exact nightmare with GrowthForge on Google Play last year. the 20 testers for 14 days thing nearly killed the launch. ended up doing the same reciprocity hustle on reddit -- test mine, I'll test yours. actually found 3 people from that who became real users after launch, which I didn't expect. the bureaucracy part sucks but the community muscle you build trying to clear it is weirdly useful later

  4. 1

    The 14 day rule is genuinely underrated as a forcing function. Most founders skip proper beta testing when there is no rule forcing them. Google basically made you do the thing you should have done anyway.

    We build apps for first time founders and the ones who go through a real testing phase always launch with more confidence. The feedback from strangers hits different than from people who want to be nice to you.

  5. 1

    The closed testing phase is genuinely useful if you treat it as a real beta instead of just a checkbox. We went through the same thing with a couple of our Android apps and the feedback from strangers was night and day compared to friends. One tester found a crash on a Samsung device we didn't have, another pointed out that our onboarding flow was confusing in a way that seemed obvious once someone said it out loud.

    Interested to see the Reddit Ads post-mortem. 0.35% CTR is solid but that click-to-install gap is where most of the money disappears in my experience. The Play Store listing ends up being the real landing page and most indie devs (myself included) don't spend enough time optimizing it.

  6. 1

    PS I also really like the web design and style!

    1. 1

      Thanks for the technical audit, Hani! Really appreciate the 'quick wins'. I’ll instruct my AI assistant to implement the security headers and fix the Meta/Open Graph tags today. I overlooked the web SEO while focusing 100% on the mobile build. Cheers!

  7. 1

    Hi "keept"! congrats on your product! COuple of reco's from my side: add all missing security headers to protect against common web vulnerabilities (this is a quick win, just instruct your antigravity or whatever); and I've seen this already in a couple of other product on IH, there is missing meta description, H1 heading, and incomplete Open Graph tags (they could hurt search engine rankings and social media sharing).. other than that, good luck!

  8. 1

    congrats on clearing that hurdle - the 14-day rule is genuinely rough. 0.35% CTR on reddit is solid, the click-to-install drop usually comes from the play store listing not matching the ad hook, so testing that makes sense. fwiw i'm building sprites ai to automate meta/google paid UA for mobile apps, so i'm deep in channel quality questions too - reddit tends to have decent CTR but weaker install intent than search-based channels. are you planning to test any other channels alongside reddit, or doubling down here first?

    1. 1

      Great insights, Anna! You're spot on about the intent gap. I'm currently auditing my Play Store listing to make it align better with the 'Administrative Debt' hook. As for other channels—I'm looking into Search Ads next, but I want to 'plug the leak' on Reddit first since the CTR is so promising. Sprites AI sounds interesting, I'll definitely check it out!

  9. 1

    Feels like the hard part isn’t keeping things, but deciding what actually matters over time.

    Do users tend to accumulate more and more, or if they actively filter things down?

  10. 1

    Just cleared this hurdle myself a few weeks ago for my family calendar app. The rule is 12 testers now (they lowered it from 20) — already way more manageable. 12 people you actually know is doable. 20 was pushing it.

    The hardest part wasn't finding 12 people — it was keeping them engaged for the full 14 days. A lot of people install and forget.

    One thing I'd add to your list: friends are too nice to give you honest feedback. Strangers actually use the app the wrong way — and that's where you find the real bugs.

    Congrats on shipping — curious to hear how the Reddit Ads experiment goes. Keen to see if it's worth it for a B2C app at early stage.

    1. 1

      Congrats on clearing your hurdle too! 12 sounds way more humane, but I decided to aim for 20+ just to have that 'safety margin'—Google's algorithms can be unpredictable, and I didn't want to risk a reset on day 13!

      You are 100% right about the feedback. My friends were like 'Cool icon!', but the strangers from App Hive were the ones who told me my FX conversion logic for ZAR was confusing. That's the real value of the 'purgatory' phase.

      About Reddit Ads: I'm exactly $12 into the experiment right now. The CTR is surprisingly solid (around 0.35%), which tells me the 'Administrative Debt' hook works. However, turning those clicks into actual installs is the real challenge. I’m currently tweaking the Play Store listing to see if I can plug the leak.

      I'll post a full 'Post-Mortem' of the ad spend here in a few days. Stay tuned!

      1. 1

        Wow, 0.35% CTR on Reddit Ads — honestly more than I expected. Most benchmarks I've seen are around 0.1-0.2%. The hook is clearly working.

        Interesting timing for me too. I'm currently figuring out the best distribution channels for my own app, and Reddit Ads wasn't even on my radar. Now I'm watching your experiment closely.

        Looking forward to the post-mortem.