I built my first app and discovered that getting people to see it might be harder than building it

Every founder hits this wall. You finish the hardest technical hurdle of your life, and then you discover that building was the comfortable part.

The reason communities delete project links is that moderators see fifty billboard posts every day. The moment a post feels like an announcement, spam filters trigger.

Three shifts that helped me get traction without feeling like a spammer:

1. Stop telling developers to try your consumer app. Developers love talking about architecture, but they are almost never your actual target user. For multilingual chat, your audience is mixed nationality couples, expats dealing with local landlords, and language exchange learners. Find their specific Discord groups and forums instead of general startup boards.

2. Share the engineering breakdown instead of the app link. If you write: I built a translation app, check it out, it gets removed. If you write: Here is how I handled live socket translation latency under 200ms and what it cost on API tokens, developers will upvote it and naturally click your profile to see the demo.

3. Answer active complaints in niche groups. Search Reddit or forums for people asking how to chat with a partner whose parents speak another language. Drop a direct, helpful comment explaining how you solved that exact issue. One genuine recommendation to a person with an active problem is worth a hundred broadcast posts.

One part of this may be activation rather than visibility: a chat app cannot really be experienced by one person alone. When someone installs HEYID, do they already have a specific person they want to invite, and can that second person join with almost no friction? I’d test recruiting pairs around one concrete situation—language partners, mixed-language families, or international teams—rather than recruiting individual users. Have you seen any use case where both sides joined and actually completed a conversation?

IH, Reddit, X, doesn't really matter which one. Distribution costs something everywhere. On most platforms you pay with money. Here you pay by showing up for a while first, which is cheaper but slower, and because it doesn't feel like paying it feels unfair.

The part I'd separate out: building the app and getting people to use it are two different jobs. You just finished a hard one and you're standing at the beginning of another one that has almost nothing to do with it. That gap is what you're feeling, not the moderators.

Congrats on shipping though. Months of learning things you'd never touched before is the actual achievement here.

I really relate to this. I’m building an app myself right now, and I’m starting to realize that building the product is only half the challenge.

You spend months learning, fixing bugs, and getting something to actually work, then suddenly you have to figure out how to get it in front of people without coming across as spammy or getting blocked for self-promotion.

It’s a strange problem because as a small indie developer, you’re not really “advertising” in the traditional sense, you’re often just trying to find a few people willing to try what you made and give honest feedback.

Still figuring out the distribution side myself, so it’s reassuring to know I’m not the only one feeling this way. Good luck with HEYID!

Paweł — I felt this one. I'm building a browser extension
solo, and the exact thing hit me: I spent months getting
the product right, then discovered that getting anyone to
see it is a whole different mountain. You're not looking at
it wrong — this surprises almost every first-time builder,
and it's genuinely the harder half.

A few honest things I've learned (still learning):

The "you can't promote here" walls are real, but the trick
is that communities don't mind you sharing when you show up
as a person working through something, not as an ad. The
posts that get removed are "check out my app!" The posts
that get welcomed are "here's what I built, here's what I'm
struggling with, what would you do?" Same product, totally
different reception. Lead with the honest story and the
struggle, not the pitch — ironically that gets people to
actually look.

This post you just wrote is a perfect example. It's honest,
it's vulnerable, it's not an ad — and it made me want to go
look at HEYID. That's the move. You're already doing it
right here without realizing it.

The other thing: you don't need "an audience" to start —
you need a few real people who care. Not thousands. Three
people who use it and tell you the truth is worth more than
a viral post. Go where people already have your problem
(for a cross-language chat app, maybe language-learning
communities, expat/immigrant forums, travel groups) and
show up genuinely, not to promote but to be part of it.

It doesn't get easy, but it does get less mysterious. You
built the hard thing. This is just a different hard thing,
and it's learnable. Rooting for you.

Living this right now, word for word. The build took days, getting anyone to notice it is taking weeks and counting. Did you find anything that actually moved the needle, or still figuring it out too?

I felt this post in my bones — I shipped my first web app a week ago (a free golden-hour tool), and the "now what" after building was genuinely more disorienting than building it. Three things that are actually working for me so far, in case they help:

1. Stop asking for attention, start making yourself searchable. I stopped posting "check out my app" and started writing long-form content on my own domain — 160 city pages and one article a day. The distribution question becomes an SEO question: someone who searches "golden hour in Tokyo" needs exactly what I built. No moderator can remove that.
2. Only go where your product is the answer. My first real traction came from dev.to, not launch communities — because the tool has a free public API, a post about it there is content, not advertising. For HEYID: skip r/android and the launch lists. Find the exact moment you described — travel groups, expat forums, parents with kids in foreign schools — and be the answer to "how do we talk to this person who doesn't speak our language?"
3. The ban/delete/restriction loop is real, and it's not you. Every serious indie has eaten that. It's a filter working as designed — the fix is being the reply to an existing question, not the announcement.
   HEYID is a genuinely good first idea — cross-language chat is a real pain. The wedge problem is real, but so is the demand. Keep going.

The rule you keep hitting is not aimed at you. It is aimed at the shape of the post.

"I built something, please try it" puts you at the centre. Every community filters that, because if they did not, the whole forum would be people standing in a row holding their own apps. But the same communities are full of people asking questions, and nobody has ever been banned for answering one well.

So invert it. Find the threads where someone is stuck on the problem your app solves, and answer that person's actual question, in full, whether or not they end up using your thing. Say what you built only if it is the honest answer, and after the useful part. People then click your name, and your profile is where the link belongs. Nothing gets removed, because you were not promoting.

I am doing exactly this right now. I have run software on my own since 2004 and I have never made a sales call in 22 years, but everything I built was in Japanese, so to an English speaking audience I do not exist. I am not launching at people. I am answering questions for a while, in this community and two others, and treating that as the cost of being new here.

The slower path is also the one that survives. A promotional post is dead the day it is posted. An answer sits there for years and keeps sending people who arrived with a problem you already solved.

You already have one channel where nobody can ban you: the Play Store itself. People search "translate chat" with intent — invest two weeks in the listing (real mixed-language conversation screenshots, Polish + English keywords) and watch installs come from search, not from community posts. Search intent doesn't need a moderator's permission.

The rule isn't really no promotion, it's no withdrawals before deposits. I started my last company doing free IT migrations for companies displaced after 9/11, and every paying client came from someone I had already helped, not from anyone I pitched. Write the post about what you learned making real-time translation work in a chat app, put the link at the bottom, and the moderators stop caring.

a chat app cant be tried alone tho. the dev communities u keep posting in are full of solo ppl, so even someone who likes it has nobody to message.

The discovery that distribution is harder than building is one of the most universal moments in indie hacking. Almost everyone hits it, usually around month 2 or 3.

What tends to work better than announcing yourself across platforms: find the communities where your specific user already exists and become a genuine participant before you ask anyone to try anything. For HEYID specifically, language learning communities, expat groups, and people who regularly deal with cross-language communication problems are where the people who actually need this are. Those communities tend to welcome real conversations, not product posts.

You don't need algorithm permission when you're already talking to the right people.

The phrasing "getting people to see it" masks a measurement problem. Visibility and activation are different signals. Communities reject the app because "here's what I built" doesn't tell someone why their life changes if they try it.

Translation is feature; cross-language family communication is the use case. The test isn't whether more people see HEYID, it's how many people who encounter it in context (Reddit thread: "parent learning child's language," Quora: "how to understand my immigrant partner") try it. That measurement is your real constraint, not visibility.

Paweł, congratulations on actually shipping it. Plenty of people learn the technologies and never get as far as the Play Store, and a chat where two people don't need a shared language is a genuinely good reason to have put yourself through all of that.

The second thing you ran into is real, and I hit the same wall this week from the other side of it.

I'm building a price-history tool and went into a handful of niche Facebook groups hoping to find early users. In one group I read the rules before posting, and rule 3 said in plain words that advertising any deals website was forbidden. Another group's rules said "we will block you if you comment or post links". I would have been removed inside a day and probably never understood why.

What I've settled on, and I'm early enough that I can't promise it works yet: don't arrive with the project at all. Find the posts where somebody is already asking out loud the question your product answers, and answer it properly, for free, with no link attached. In my case people ask "is this price actually any good?" and I have 30 days of recorded prices that can answer it in a single comment. If anyone wants to know where the numbers came from, they ask me.

It is far slower than posting a launch. But it's the only version I've found that the moderators of a good community actually want in their group, and honestly it makes sense that they do.

Hope HEYID finds its people. What's the closest thing to a working channel you've found so far?

I get it; I’m in the same boat. I built an AI-powered CV analyzer—mostly just for the sake of doing something—but then I decided to take it further and turned it into a website. However, getting an audience for it is really tough.

I think the mistake is treating distribution as “finding places where I’m allowed to promote my product.”

For a product like HEYID, I’d start with the specific problem — people trying to communicate across language barriers — and find conversations where that problem already exists.

Instead of posting “I built an app,” contribute to those conversations first and let the product become the relevant solution when it genuinely fits.

That also gives you a better signal than launch-post visibility. If people who already have the problem click through, try it, and come back, you’ve found a promising audience. If they don't, you learn something about the positioning before spending money on promotion.

The goal isn't to find a platform that allows promotion. It's to find people who already have the problem.

After building/running my first SaaS for 15 years, I'm experiencing the same thing you are with new projects. Times have changed. It can be frustrating.

I don't think you're looking at distribution wrong. I think the honest answer is that it's genuinely harder for solo builders now than the "just build it and they will come" era suggested. Algorithms and moderation exist to fight spam, but they can't tell the difference between someone farming links and someone like you who spent months learning from scratch to ship something real.

For what it's worth, this post itself is a good example of the way in. It doesn't read as promotion; it reads as someone being honest about a real problem. That's usually what gets people to actually look at what you built. Wishing HEYID good luck; the language-barrier problem it's solving is real.

The cold-start distinction I’d make is reach vs. qualified activation: choose one narrow use case and measure completed task, invite, or repeat use instead of impressions. Before posting anywhere, talk to 10–15 people who already describe that pain in their own words, then publish the smallest example that answers that exact question; it gives communities something useful to react to without turning the post into an ad. A repeatable channel is one where those conversations produce referrals or returning users, not merely a one-day spike.

I opened the English site and noticed the Premium benefits are still being finalized. I'd finish that section with the actual free limits, then choose one of your use-case pages and show a real translated conversation on it. Track how many visitors reach the Play Store from that page. Are any of those pages already getting search impressions?

Same wall, from the other side of it right now: I'm working through outreach for a pre-launch Mac Mini rental service, and almost every community I've tried — this one included — gates new accounts from posting until you've built up genuine, non-promotional activity first. It's the right call, I get why it exists, but it does mean the actual "I built this" moment gets pushed back by days or weeks of doing something else first. What's helped me is only commenting where I actually have an answer or a real question, not just padding a count. Still an open question for me though: once you are allowed to post, does leading with the problem (two people who can't talk to each other) work better than leading with the app itself? Curious if you've tried framing it that way anywhere yet.

Yeah, this is real and it gets worse the smaller you are. Most communities have some version of 'no self promo except in this one thread on this one day,' so you get seen for maybe 30 minutes a week if you're lucky.

What's worked better for me than blasting general dev communities: find the handful of places where your actual users already hang out, not developer forums, but people who'd actually want a translation free chat app. Go there first even if it's slower. Getting banned from a generic sub costs you nothing since those weren't your users anyway.

For what it's worth, this exact problem is part of why I ended up building something for myself too. You're not imagining the wall, it's a real gap.

Yoo, am new here an amazing really glad that I joined this community of great individuals.
Just wanna ask what your new app all about?

Same cold-start pain is extremely common. What usually works better than blasting "I launched": join communities as a helper first, answer adjacent questions, and only share the app when someone has the exact problem. Also try non-link posts (screenshot + lesson learned) and put the store link in a comment if the platform filters outbound links. Distribution is a skill you build after shipping — annoying, but normal.

I’ve found the same with a privacy-first tracker: explaining the local-only/no-login choice in a discussion about the underlying problem works far better than dropping a launch link, and small relevant communities have been more useful than broad promotion.

The question you asked is the one I got stuck on too: where are you allowed to say you built something.

On a small X account this week, my own posts sat at 62–222 impressions. One reply under someone else's tweet shows 2,821 views. That reply produced 4 profile visits. Being seen inside a thread is not the same as people coming to look at me, and it is not the same as announcing an app in a community that bans announcements.

I stopped leading with "I built this." I look for the moment someone already named the failure — two people who cannot talk, a trip that died in the comment box — and I answer that line. Searchers on the Play Store arrive with intent. A conversation that already has the problem in it does too.

If a community deletes the launch post, that is the filter working. It is not proof nobody wants the chat. It is proof that "I shipped an app" is the wrong sentence to lead with.

Omri and aryan are both pointing at the same thing from different angles, and it's worth naming directly: "getting people to see it" is a proxy metric, and proxies feel like progress precisely because they're easier to move than the real thing. Ran into this myself this week from a different angle — banned from Reddit for trying to increase visibility, and even before the ban, more views were never going to tell me whether anyone would actually use what I built. Seeing and acting are different signals, and it's easy to optimize the one you can measure instead of the one you actually need.

minchan's reframe is the actionable version of that: don't try to get more eyes on the whole app, find the one specific moment people fail at (parent-child language gap, immigrant partner, whatever's most concrete) and show up in the conversation already happening around that exact moment. Ten focused conversations beating ten launch posts isn't just a distribution tactic, it's also the faster way to find out if you're even solving the right problem — which is a separate and arguably more important question than "how many people saw this."

The most reliable path I’ve seen from zero is to treat distribution as a sequence of small, permissioned experiments rather than a launch announcement. Pick one job-to-be-done (for example, translating chat for Polish/English families), write 5–10 genuinely useful answers around that problem, and measure qualified visits → activation → repeat use; the channel is only working if those downstream steps move. A store listing can capture search intent while communities supply research, not a pitch. That gives you a path no moderator has to approve while also teaching you who the product is really for.

The distribution problem may be real, but I’d separate “people aren’t seeing it” from “people see it and don’t act.” When someone who isn’t a friend or fellow developer actually encounters HEYID, what are they doing next?

Yep, this is exactly why launch surfaces that create a reason to participate can work better than raw self promo. For SaaS founders, a playful angle like BuilderBench is interesting because the promo is earned by competing: eight quick events, one all-round score, top-five SaaS links. https://www.buildersbenchmark.com/

The mistake is treating ‘showing the app’ as the unit of distribution. Communities reject product announcements because they ask for attention before offering context. Start with the exact moment when two people fail to communicate across languages—travel, school parents, customer support, or something else. Pick one, find conversations where people already describe that problem, and contribute the product as part of the answer. Ten conversations with one narrow group will teach you more than ten launch posts. The app can be broad; the first distribution wedge should be painfully specific.