8
101 Comments

I built a global chat. Now I have to solve the empty room problem.

My name is Paweł and I'm building HEYID, a chat app for meeting people from around the world.

The funny thing is that building the app was probably the easier part.

Now I'm facing a problem that you can't really solve with more code.

The empty room.

If you open a normal website and there are no users, it's not a huge problem.

If you open a chat app and there is nobody to talk to, the product feels broken.

And HEYID has an even bigger version of this problem because it's global.

Imagine opening the app from Poland and wanting to talk to someone from Japan.

If there are no Japanese users online, the translation doesn't matter.

Voice translation doesn't matter.

AI suggestions don't matter.

The whole product depends on another human being being there.

That's the part of building a social product I didn't fully understand when I started.

I spent months thinking about features.

Chat.

Translation.

Voice messages.

Language detection.

AI suggestions.

Profiles.

Search.

Premium.

And then I realized:

The most important feature is people.

😂

Now I'm spending much more time thinking about distribution than I expected.

Where do people who want to meet people from other countries actually hang out?

What makes someone stop scrolling and think:

"Yeah, I'd actually try this."

How do you get the first 10 people into the same place at roughly the same time?

How do you create conversations instead of just downloads?

And how do you do it without turning every social network into a giant advertisement for your app?

I'm still figuring this out.

I've been experimenting with Indie Hackers, social networks, SEO and different communities.

Some things worked better than I expected.

Some things got absolutely nothing.

And some of my "great ideas" produced basically zero response. 😅

But I think this is one of the most interesting parts of building a social product.

You're not only building software.

You're trying to create a small ecosystem where the software becomes useful because other people are there.

That's a completely different problem from writing code.

I'm curious how other founders dealt with their own "empty room" problem.

How did you get your first real users to actually interact with each other?

HEYID is live if anyone wants to see what I'm building:

https://heyid.online

I'm Paweł, building this from Poland, and I'll be around in the comments.

on September 24, 2026
  1. 1

    The "empty room" problem is the part of building a social product that no amount of engineering solves, and I think you nailed the real reason: for most products, being early is annoying. For a chat app, being early is fatal. The user doesn't see "we're just getting started." They see "broken."

    You said the most important feature is people, and that's the whole game in one sentence.

    One thing worth thinking about: you can't solve cold start by getting 10,000 users. You solve it by getting 10 users into the same room at the same time, on purpose. The trick most social products miss is that the first cohort should be designed, not acquired. Pick a specific shared interest, a specific time window, a specific reason to be there — "Japanese and Polish language learners, Tuesday at 8pm UTC" — and let that cohort grow organically. It feels artificial, but it works better than any ad.

    Question for you: how are you thinking about the ratio of real users to bots or seeded conversations? Every social product I've looked at faced this — some seeded content, some didn't. Curious which side you land on.

    The translation angle is genuinely interesting, by the way. That's the part of HEYID that could be a real wedge, if you can find the room where people actually want it.

    Following along from Tunisia. Cold start is the hardest problem in product — respect for attacking it directly.

  2. 1

    Dealing with the same cold-start problem on a fanbase-battle site. Two things helped more than any channel:

    1. Never show an empty room. The arena opened with a small starting allocation (disclosed in the rules), so the first visitor sees a race, not a void.
    2. Make the first action about someone else: every team shows "X seats to pass [rival]". Rivalry gives people a reason to act before anyone else is there.

    For a chat, maybe the equivalent is a scheduled "room of the day" with a fixed topic and time, so 5 people overlap instead of 50 spread out. Curious which language pair gets you the most overlap so far?

  3. 1

    This is useful. How are you finding your first users so far?

  4. 1

    Really relatable. How much time do you put into this each week?

  5. 1

    This is useful. How are you finding your first users so far?

  6. 1

    This is useful. How are you finding your first users so far?

  7. 1

    Really relatable. How much time do you put into this each week?

  8. 1

    This is useful. How are you finding your first users so far?

  9. 1

    I'd solve this with time instead of geography: give people a reason to show up at the same clock moment, like a nightly scheduled "global hour," so density happens on a schedule instead of hoping enough strangers are online at once. When we launched SocialPost.ai, founders showed up reliably for a scheduled thing, a live cohort, a fixed posting window, far more than for an always-on tool with no reason to open it right now. Manufacture the coincidence instead of waiting for it.

  10. 1

    what i have learned is first thing first before any development is getting the right users radar then channel your app towards that position

  11. 1

    I’d treat this as a density problem before a distribution problem: pick one narrow corridor and a recurring 30-minute window, then recruit both sides specifically for that session. Measure the percentage of sessions that produce a two-way exchange within 60 seconds, median wait time, and seven-day return rate—not downloads. If the other side is missing, a visible queue or scheduled match is better than pretending the room is live. Once one corridor has repeatable liquidity, copy the playbook to the next corridor instead of opening the whole world at once.

  12. 1

    Not to sound harsh, but this is the third post mentioning the problem with distribution, saying the built part was easy. What "founders" stopped doing today is to have their idea validated by potential users prior to building a product. Since it is so easy to build an app nowadays, many developers build one in a weekend. Yet it doesn't mean there is need for such an app.

    How did you realize there was need for an app like this given we have all these social media available?

    To actually give you some advice; try to go to different communities across platforms like Internations or other travel related platforms, which gather users from all around the world and organize webinars, offline events for them. Join them and ask them if they would use it for connecting with each other or even offer it to Internations as a product they could use across their global platform.

  13. 1

    The “empty room” problem is brutal for social products because users judge the product by who is there, not just by how well the app works.

    I’d probably focus on creating density in one small community, timezone, or use case first instead of trying to make the whole global network feel active from day one. Once one pocket feels alive, expansion becomes much easier.

  14. 1

    The empty-room problem is probably the hardest part of something like this. Getting people to sign up is one thing, but getting enough of the right people there at the same time is a different problem.

    I’d probably start much narrower than “global chat” and focus on one type of person or use case first. Then figure out where those people are already looking for ways to meet others internationally. That might give you some interesting distribution opportunities beyond just promoting the app itself.

  15. 1

    The “first 10 people in the same place at the same time” framing is spot on. Have you found a small recurring time window or country pair that creates enough density to make the first session feel alive?

  16. 1

    Eye opening - better tech does not instawin audiences in the room...
    As a lifelong techie comms guy - I hadn't considered this... so now I have to figure out how to sleep again after reading this.

    Good work and keep up the effort! We need more of this.

  17. 1

    I build directory software, and directories live with this exact problem - a directory with no listings is as dead as a chat with no people. The industry answer is to seed the supply side before anyone arrives: the content exists before the community, so the first visitor never sees an empty room. You can't seed humans, and the "make the room smaller" advice already here is right. What I'd add: you can seed the reason to be there. A chat that's just "come talk" needs a crowd; a chat with a fixed ritual - one hour, one prompt, one host who opens the room every day - needs twenty. The ritual is the listing. If you had to pick one recurring window and one conversation prompt to run every day for a month, what would they be?

  18. 1

    For a global chat, I'd start with one narrow recurring window rather than global coverage. Pick one corridor and schedule a 30-minute live room around an existing community ritual, then measure conversations per active minute rather than signups. If that works, expand corridor by corridor.

  19. 1

    The "make the room smaller before you make it bigger" advice above is the answer — I'd just add one thing: schedule the room. Pick a weekly one-hour slot, announce it everywhere, and be there yourself every single time. An empty room that fills up predictably beats a 24/7 room that's empty 23 hours a day. People don't join empty spaces; they join events.

  20. 1

    This is useful. How are you finding your first users so far?

  21. 1

    Interesting approach. What was the hardest part to get right?

  22. 1

    Really relatable. How much time do you put into this each week?

  23. 1

    This is useful. How are you finding your first users so far?

  24. 1

    This is useful. How are you finding your first users so far?

  25. 1

    This is useful. How are you finding your first users so far?

  26. 1

    Really relatable. How much time do you put into this each week?

  27. 1

    Interesting approach. What was the hardest part to get right?

  28. 1

    Really relatable. How much time do you put into this each week?

  29. 1

    This is useful. How are you finding your first users so far?

  30. 1

    This is useful. How are you finding your first users so far?

  31. 1

    Interesting approach. What was the hardest part to get right?

  32. 1

    This is useful. How are you finding your first users so far?

  33. 1

    This is useful. How are you finding your first users so far?

  34. 1

    Really relatable. How much time do you put into this each week?

  35. 1

    Interesting approach. What was the hardest part to get right?

  36. 1

    Really relatable. How much time do you put into this each week?

  37. 1

    This is useful. How are you finding your first users so far?

  38. 1

    Interesting approach. What was the hardest part to get right?

  39. 1

    This is useful. How are you finding your first users so far?

  40. 1

    Interesting approach. What was the hardest part to get right?

  41. 1

    This is useful. How are you finding your first users so far?

  42. 1

    This is useful. How are you finding your first users so far?

  43. 1

    Really relatable. How much time do you put into this each week?

  44. 1

    This is useful. How are you finding your first users so far?

  45. 1

    Really relatable. How much time do you put into this each week?

  46. 1

    This is useful. How are you finding your first users so far?

  47. 1

    Interesting approach. What was the hardest part to get right?

  48. 1

    This is useful. How are you finding your first users so far?

  49. 1

    Interesting approach. What was the hardest part to get right?

  50. 1

    Really relatable. How much time do you put into this each week?

  51. 1

    This is useful. How are you finding your first users so far?

    1. 1

      shit bot

  52. 1

    Interesting. How are you measuring whether it is working?

  53. 1

    How did you decide this was worth building in the first place?

  54. 1

    This is useful. How are you finding your first users so far?

  55. 1

    Interesting approach. What was the hardest part to get right?

  56. 1

    This is useful. How are you finding your first users so far?

  57. 1

    This is useful. How are you finding your first users so far?

  58. 1

    Really relatable. How much time do you put into this each week?

  59. 1

    Really relatable. How much time do you put into this each week?

  60. 1

    This is useful. How are you finding your first users so far?

  61. 1

    Interesting approach. What was the hardest part to get right?

  62. 1

    This is useful. How are you finding your first users so far?

  63. 1

    What made you pick this stack over the alternatives?

  64. 1

    Good point. Did you test that with users before committing to it?

  65. 1

    Good point. Did you test that with users before committing to it?

  66. 1

    Appreciate the honesty here, most people only share the wins.

  67. 1

    This is useful. How are you finding your first users so far?

  68. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  69. 1

    Great breakdown. What feedback have you had from early users?

  70. 1

    This is useful. How are you finding your first users so far?

  71. 1

    Interesting approach. What was the hardest part to get right?

  72. 1

    Really relatable. How much time do you put into this each week?

  73. 1

    This is useful. How are you finding your first users so far?

  74. 1

    Really relatable. How much time do you put into this each week?

  75. 1

    This is useful. How are you finding your first users so far?

  76. 1

    This is useful. How are you finding your first users so far?

  77. 1

    Interesting approach. What was the hardest part to get right?

  78. 1

    This is useful. How are you finding your first users so far?

  79. 1

    This is useful. How are you finding your first users so far?

  80. 1

    Really relatable. How much time do you put into this each week?

  81. 1

    Interesting approach. What was the hardest part to get right?

  82. 1

    Make the room smaller before you make it bigger. A global chat with 30 users is empty 23 hours a day, but the same 30 people booked into one hour feel like a crowd.

    Concretely: pick one language pair and one time slot (for example Polish and Japanese learners, twice a week at a fixed hour) and announce it as an event, not an app. Language-exchange groups already run scheduled sessions like that, so that's where the first ten are. Once a slot fills reliably, add a second one. Open "anytime" chat only when the scheduled slots are overflowing.

    The download count doesn't matter much until two people are reliably there at the same time.

  83. 1

    This is useful. How are you finding your first users so far?

  84. 1

    Interesting approach. What was the hardest part to get right?

  85. 1

    Curious how long it took before you saw the first real results?

  86. 1

    Interesting. How are you measuring whether it is working?

  87. 1

    Interesting approach. What was the hardest part to get right?

  88. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  89. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  90. 1

    Have your experiments revealed a specific user or geographic group that creates conversations reliably, or are you still seeing downloads without enough simultaneous activity?

  91. 1

    This is useful. How are you finding your first users so far?

  92. 1

    This is useful. How are you finding your first users so far?

  93. 1

    Interesting approach. What was the hardest part to get right?

  94. 1

    Really relatable. How much time do you put into this each week?

  95. 1

    Really relatable. How much time do you put into this each week?

  96. 1

    This is useful. How are you finding your first users so far?

  97. 1

    Interesting approach. What was the hardest part to get right?

  98. 1

    This is useful. How are you finding your first users so far?

  99. 1

    one thing that helped us with the same problem: make it worth opening even when nobody is there. something a person can do solo, so the first visitor doesnt bounce. and then pick one fixed hour a day when you personally show up to talk. 10 people at the same time beats 100 spread over a week

  100. 1

    This is great work — what's the biggest thing you'd do differently if you started over?