People ask for app recommendations on Reddit every day — “best app for tracking workouts?”, “is there an app that does X without a subscription?”, “what do you use for budgeting on Android?” These are buyers mid-decision, and the app they pick is usually the one a real person recommended in the thread. But apps are also the thing Reddit is most suspicious of: every community has seen a hundred developers drop a link and disappear. Promoting an app on Reddit works when you act like a member of the community who built something useful, not like a download link with a username. This guide covers the whole method — finding recommendation threads, demo and showcase etiquette, feedback threads, beta testers, and launch posts — the way Alrebro does it.
1. Find people asking for recommendations
The best threads for an app are the ones where somebody asks for a recommendation and describes what they need. Start with the problem words, not your app's name: the job the app does, the frustration with the current options, the platform (iOS, Android, web) they are on. Alrebro reads your website when you create a project, pulls out those problem words, and searches your tracked communities for threads that use them — then labels each thread by intent, so the “what app should I use for X?” threads come first. If you are doing it by hand, the subreddit finder takes a description of your app and shows the communities where people talk about that problem.
Read the thread before you reply. An asker who wants a free app with no account is not your customer if your app needs a subscription and an account — saying so honestly costs you nothing and saves the thread from a misleading recommendation. An asker who tried your three biggest competitors and hated all of them is the best thread you will find all week: they have already told you exactly what is wrong with the market, and your answer can speak to it directly.
2. Pick the right communities with the finder
App communities are narrower than they look. There are big general communities where people ask for app recommendations, and small niche ones built around one activity — running, budgeting, language learning, photo editing — where the users are far more serious and the recommendations stick. The niche ones are usually better: fewer threads, but every reader is your exact user. Use the finder to build a list of both, then check the Rule Book for each one before you post anything. The Rule Book gives every community a risk level — Safe, Careful, or Dangerous — based on its promotion and link rules. A community that bans self-promotion is not a challenge to work around; it is a community to leave alone.
Do not trust a community's name alone. Some communities with a general-sounding name are strict about apps, and some niche ones welcome developers. The only reliable check is the rules — read them, and read the Rule Book summary that Alrebro keeps for each tracked community. Member counts and activity numbers change constantly, so verify them live on Reddit itself rather than trusting any number you read elsewhere — including here.
3. Demo and showcase etiquette
Some communities have a weekly showcase, demo, or “show off your app” thread, and some ban demo posts entirely. The rule is simple: only post a demo where the rules explicitly allow it, and only in the place the rules point to. A demo post in the wrong community gets removed and marks your account; the same post in the weekly thread gets real users. When you do post a demo, show the app doing the job — a short description of the problem it solves, what it looks like in use, and what is free versus paid, stated plainly. No hype, no “revolutionary”, no fake claims about downloads or ratings. The post generator can draft a showcase post in one of three tones and check it against the community's rules first — use it as a starting point, then edit the draft until it sounds like you.
Never post the same demo in five communities on the same day. Space them out, and only post in communities where you are already a member. If a community has no showcase thread and its rules say nothing about demos, assume the answer is no until you have seen a demo post stay up there — posted by someone else, not by you.
4. Feedback threads: ask for feedback, not downloads
The most effective way to promote an app on Reddit is to ask for feedback instead of downloads. A post that says “I built this app for X, what am I missing?” invites people to try it, criticise it, and — if it is good — recommend it. A post that says “download my app” invites removal. Feedback threads work best in the community the app is for, not in a general app-promotion community: runners will tell you what a running app is missing; strangers in a promotion thread will not. Ask a specific question — “does the export flow make sense?”, “is the free tier enough for your use?” — because a vague “any feedback welcome” gets vague answers.
When people reply, answer every comment, including the critical ones. Thank the person who found a bug, fix it if you can, and say so in the thread. That follow-up is the promotion: people who see a developer listening will try the app, and some of them will mention it in the next recommendation thread without you asking. Draft Studio can help you write the feedback post and the replies, in a tone that sounds like you — but the answers to people's comments should be yours, written by you, in the moment.
5. Recruiting beta testers without looking like spam
Beta testers are the one case where you can ask people to try your app directly — but only in the right place and the right way. Some communities allow beta-test calls; many do not. Check the Rule Book first, and if the community bans it, do not post. When it is allowed, say exactly what the beta is: what the app does, what is unfinished, what you need testers to do, and what they get — usually free access for a period, stated plainly. Cap the number of testers you ask for. “Looking for ten people to try this” is a real request; “looking for testers” with no limit looks like a download drive.
Do not message people privately to ask them to test your app. Unsolicited direct messages about a product are spam by Reddit's own rules, and they get accounts reported fast. Keep every beta invitation in the open, in a thread where it is allowed, and let people come to you. The pipeline board in Alrebro tracks the threads where you invited testers, so you can follow up with the people who replied instead of inviting the same community twice.
6. Launch posts — only where allowed
A launch post is a one-time event, and it only works once, so do not waste it on the wrong community. Post it where the rules allow launch or release announcements, and nowhere else. The post should say what the app does, who it is for, what it costs, and what changed since the beta — the facts, not the sales pitch. If the community allows a link, include one; if it does not, do not try to smuggle one in through a comment. And do not launch the same app in the same community twice. A second launch post a month later is spam, even if the first one did well.
Before launch day, warm up the account. Alrebro's warm-up coach runs a 14-day checklist: join the communities, read the rules, leave genuine comments without mentioning your product, answer questions from experience, and check your account health before you post anything promotional. A launch post from an account with two weeks of real activity reads completely differently from one posted by an account created that morning. Check the shadowban checker first — if the account is shadowbanned or not found, fix that before launch day, not after.
7. Draft replies in three tones, then post them yourself
Recommendation threads are where most of your installs will come from, and they need a different reply than a feedback thread. Draft Studio writes the draft in one of three tones — helpful-expert, friendly, or concise — and checks it against the community's rules. Answer the asker's question first, explain why from your own experience, and mention your app only if it is the honest answer to what they asked. Then post it yourself, from your own account. Alrebro never auto-posts: Reddit bans fully automated posting, and a tool that posts for you gets your account banned. There is no setting that changes this, on any plan. Posting manually also keeps you honest — you see the other answers, and if three people already recommended better apps, the right move is to skip the thread.
Never copy-paste the same reply into several threads. Reddit's filters notice identical text, and so do the humans reading it. Every reply should be written for that thread, even when the draft started from the same template — especially the part where you say why your app fits what this particular person asked for.
8. What to do in week 1 vs week 4
Week 1 is setup, not selling. Create your project, find your communities with the finder, read the Rule Book for each one, and start the warm-up checklist. If your account is already established, your week 1 is different: work through your first Today plans and answer a few recommendation threads a day. Run one feedback thread in your best community toward the end of the week — it will tell you more about your app than a month of guessing, and the people who reply become your first real users.
By week 4 you should have a routine: open the Today plan, answer the best recommendation threads, check the pipeline for follow-ups, and run a feedback or beta thread only when the rules allow it and you have something new to ask about. You will know which two or three communities give you real users and which ones only give you upvotes, and you will have stopped wasting time on the second kind. The Radar shows whether your app is being mentioned in AI search answers and across your tracked communities, so you can see whether the recommendation threads are compounding into real visibility.
9. What “good” looks like
Good is not a launch post with a thousand upvotes. Good is a steady trickle: a few recommendation threads a week where your app is mentioned — sometimes by you, sometimes by a user you earned in a feedback thread — almost none of your posts removed, and installs that arrive over days rather than in one spike. Good is an account that is still standing after a month, with karma earned from helpful comments. Good is a feedback thread where people told you hard truths and you fixed something because of it.
The warning signs are easy to spot: posts removed the same day you made them, comments calling you a spammer, a feedback thread with no replies at all. A feedback thread with no replies usually means you posted it in the wrong community, or you asked for downloads instead of feedback. Read the rules again, pick a better community, and ask a sharper question next time.
10. The risks, honestly
Moderators can remove your post for any reason, and Reddit itself can suspend or ban your account — Reddit decides, not Alrebro, and no feature can protect an account that breaks a community's rules. The Rule Book, the warm-up checklist, and the manual-posting rule keep the risk low, not zero. The full safety page at /safety explains the promise in detail. The most common ways app developers get into trouble are predictable: launching from a brand-new account, posting the same demo everywhere, messaging people privately about the app, and arguing with moderators after a removal. Every one of these is avoidable — and arguing with moderators is the one that gets accounts banned fastest.
11. What Alrebro cannot promise
No tool can promise downloads, installs, or revenue from Reddit, and we do not. What Alrebro does is find the recommendation threads, check the rules, and draft the replies — the rest depends on your app, your answers, and the communities themselves. Some weeks will be quiet, and quiet weeks are not a reason to post more aggressively. If you want to see the daily routine before you pay anything, the free account runs it on your app in about a minute, the features page lists everything the app does, and the plans page shows exactly what each plan includes. Start there, answer one real recommendation thread this week, and let the routine prove itself.