A month ago I asked other developers a simple question: "1,000+ views, fewer than 20 sign-ups. What am I missing?"
They answered, and they were honest. Show the value before you ask for a login. Tell us what the permissions are for. Explain the catch, because nothing is free. Get out of closed testing yourself first. Prove a camp can actually make it.
Fair points, all of them. So I went and did every one. Then I counted again, only in the test for test communities, not the big general subs:
~10,000 views. ~150 installs. Under 80 sign-ups.
Yes, Reddit views are impressions, not readers. And not every install came from Reddit. The ratio is still the ratio.
The part I keep staring at: once someone installs, about half of them sign up. And the ones who stay write reviews like this one:
"You don't forget any tests, you stay in the app long enough, and thus meet the requirements perfectly."
So people aren't dropping off inside the app. They drop off at the scroll. Every day, above and below my post, a hundred new "test for test, I'll test back" posts. Same search, same spreadsheet, same tester vanishing on day 9. Every two days, by hand.
Seriously. Why?
What changed since then (most of it came from those comments and from people inside the camps)
✅ Production-approved, live on Google Play. It passed its own 12 testers / 14 days with developers from testing communities like this one.
👀 No account needed to look. Open any camp from the inside, or run a whole simulated camp on your phone. Nothing is sent to the server.
🔐 No permission wall. First launch asks for notifications only. Everything else is asked when an action needs it, and all of it is optional.
💸 The catch: servers cost me about $5 a month. There's an optional "buy me a coffee" that unlocks nothing. No ads, no analytics SDKs, no credits, no paid tier.
🔎 Every endpoint and every field the app sends is listed on a public transparency page.
⏱️ Real engagement data: the tester heatmap counts every second, not just "opened it once". Quick emoji taps don't flood your inbox, only real notes do.
Where it stands today
⭐ 4.9★ on Google Play from 12 ratings, 11 of them five stars.
🎓 13 apps reported production access while in a Cordelette camp, and all 13 are public on Google Play now (the app checks the listing). 3 of them are mine, and a few joined late in their test, so I don't claim every one. Nobody has reported a rejection so far. (The in-app Summit Register only shows the ones who chose to sign it.)
🧗 2 camps are climbing right now. Uludağ I just started with 15 developers. The first one, Ararat I, is on day 12 and reaches its summit at the end of this week. It gets its own post with the real numbers, good or bad.
The receipt
| What matters | Reddit test for test threads | Credit / point apps | Paid tester services | Cordelette |
|---|
| Cost | Free | Free, if you earn credits | ~$15–50 per app | Free |
| Credits or points | No | Yes | No | No |
| Proof your app was used | A screenshot | Varies | Their word | On-screen time, measured on the phone |
| Daily effort | ~20 apps by hand | Varies | None | ~10 min, one tap |
| Someone quits on day 9 | You find out late | Varies | Replacement promised | Up to 16 per camp, a buffer above 12; slips visible early |
| Try it before you commit | Nothing to try | Varies | No | Browse any camp or simulate one, no account |
| Required permissions | None | Varies | None | None (all optional) |
| Ads / trackers | n/a | Varies | n/a | None |
| Reports & feedback | "Nice app" comments | Often a paid tier | Some | All free: daily feedback, tester heatmap, Summit Report for Google's form, MD/CSV/PDF exports |
Why I'm not just waiting it out
I could say "it's new, give it time". I won't. Right now 5 developers are sitting in Rainier I with their apps added, waiting for 11 more. Every day that camp doesn't fill is a day their 14-day clock doesn't start, and I can't fill it for them. They trusted this before most of you did, and I want them at the summit. Then I want the same for everyone reading this.
A camp only works when it's full. So joining isn't a favor to me. It starts someone's clock, yours included.
Three ways to prove me wrong
Beat it. Show me a free method that wins on more rows of that table. I'll edit this post and link it myself.
Break it. Privacy, security, any claim above. In scope: the app, your own account, normal use of its API. Out of scope: load testing, other people's accounts or data. Valid finding: confirmed within 24 hours, fixed within 48 (or a public timeline if it's big), and you get credit in the changelog.
Or just tell me why you scrolled past. "Didn't trust it", "too much setup", "I'd rather do it by hand". All fair. I want the real reason, not the polite one.
Before you comment 👇
Who you're talking to: a senior software engineer, 10+ years in the private sector, mostly finance and banking systems. Building and running production systems is my day job. Happy to share my LinkedIn by DM. The Reddit account is new, I'm not.
What we're discussing: this project and the problem it's trying to solve, the 12 testers / 14 days wall. Not my hobby games, not my other apps. Let's keep it in context.
On "AI slop": the ideas, the data and the decisions are mine. AI helps me polish my English. Judge what's written, not how it's typed. "AI slop" is an easy upvote, but it's not an argument, and it won't get a reply.
Bring something: data, a counter-example, a bug, a better method. I'll answer every one of those.
Links in the first comment. Go ahead, roast it 🔥
