Open discovery

Good conversations are public.

Read posts, articles, and polls from across Crowdwide. Join in whenever you are ready.

121 public conversations

Day 12 of Building Crowdwide

Hello and welcome again, devs...

Now I'm going to share the stats of Crowdwide, as you all know I do in every post:

11 members
40 posts shared
4 communities

No increase anywhere.

I'm not very happy with this... Steady growth decreases confidence and motivation.

And I made some UI improvements.

I have seen some of the icon places are empty, so I just added them up.

I have improved the feed algorithm.

I have added the help survey option in the menu so that users can access it and participate in it.

There is only 1 response in surveys...

Wow, what stats! (sarcasm)

And now I feel like it's fully polished!!

Yea, because I can't see anything that requires changes.

If you have any ideas, you can suggest them to me...

Well, well, well...

Now, if I have any updates, I will share them with you, but if not... it'll be dead... sadly.

Links 🔗

🌐 Crowdwide: https://www.crowdwide.run.place/

💻 GitHub: https://github.com/DeveloperPuneet/Crowdwide

#crowdwide #buildinpublic #opensource

1 Comments 0 Replies with a post 0 0 Views 64
Join Crowdwide to like, comment, and share

Day 11 of Building Crowdwide — Surveys Are Here!! 🚀

Hellooo... again!!

Welcome to Day 11 of building Crowdwide!

📊 Current progress

  • 11 members
  • 39 posts shared
  • 4 communities

I have noticed that I got no new members for 2–3 days...

It's looking very steady.

I didn't want to build Crowdwide like a demo project in my repo! I wanted it to be a proper platform with real users and stats.

So, I have made a few changes.

🎨 Small UI updates

First of all, I made some simple UI changes and added a specific icon for the Waves currency.

Ngl, the icon and currency are looking cool now. When I open the wallet to check if everything is good, I feel like I'm using a crypto wallet. 😂

Lol...

🗳️ Surveys are here!

Secondly, I have added a feature for getting users' opinions.

Yes, real surveys to find out why users are coming back and how they came to know about Crowdwide!

🔗 Crowdwide Surveys: https://www.crowdwide.run.place/surveys

This was suggested by MADAN DHOUNDIYAL, so I found that approach interesting, and here you go!

I have created my first survey, too.

Tbh, I have never tried getting surveys from people and using that data for actual growth. Idk how it works, but this is the first time I'm going to try it.

I'll collect the responses, analyse the results, and try to use them to grow Crowdwide better.

One more thing: only survey answers are recorded on my server. The information about whether you've already taken a survey is stored locally on your device.

So, take part in the survey, devs! ❤️

And I did nothing much other than this.

Maybe I'll find another interesting idea soon!!

#crowdwide #buildinpublic

1 Comments 0 Replies with a post 0 0 Views 66
Join Crowdwide to like, comment, and share

Day 10 of Building Crowdwide — The Newsletter Is Getting Smarter!

YAYAYAYAYA!! Welcome to Day 10 of the no-filter, no-sugarcoating series of building Crowdwide!!

Today's progress:
- 11 members
- 38 posts
- 4 communities

The progress is getting steady! Compared to days 4–6, Crowdwide is now in a much more stable state. V2 is coming on 1 November 2026, and most features are done. Only polishing remains!

Every Sunday, Crowdwide sends newsletters to subscribers. This time, I tested personalization, and it's working very well!

Previously, everyone received the same newsletter. Now, sections like For You, Trending, and You May Like make the experience more personalized. The mailing system is working fine as wine for now!

I also fixed post formatting. No more useless `#` and `**` symbols destroying your reading experience. Feeling more polished, isn't it?? Don't lie, LOL.

User suggestions 💡

Neeraj suggested targeting Discord and Telegram community owners, local businesses, and indie makers. Honestly, these ideas seem useful, especially reaching indie makers. COME ON, INDIESS!! CROWDWIDE IS BUILT FOR YOU!

Madan suggested inviting active members to co-host communities. Great idea! I've noticed 5–7 users visiting every 2–4 days, so maybe it's time to talk to them!

Midnight disaster 💀

Yesterday, emails suddenly stopped working! After checking everything, I discovered my Google Cloud OAuth refresh token had expired. Generated a new one, redeployed, and everything was working again!

One more thing: I used to write almost all my articles with AI. Now, I write them myself and only use AI for punctuation. One of my posts got 1.7K+ views in under 6 days! WOOAH!!

I won't let Crowdwide die that easily!

🌐 Website: https://www.crowdwide.run.place

💻 GitHub: https://github.com/DeveloperPuneet/Crowdwide

CRITICISE ME!!

#buildinpublic #crowdwide #opensource

1 Comments 0 Replies with a post 0 0 Views 67
Join Crowdwide to like, comment, and share

Day 9 of Building Crowdwide 🚀

So today, I thought I wouldn't write any code. All features are working, UI polishing is done, moderation is improved, and suggestions are implemented!

But then I checked Render's free-tier hours... 💀

One account had already used 560+ out of 750 hours. I thought Crowdwide might have to sleep for 8–10 days.

BUT I'M A CRUEL DEVELOPER, SO... 😭

I deployed Crowdwide from my other Render account, which had used only 250+ hours. Migrated the environment variables, tested everything, and YAHHH!! IT WORKED!! 🔥

Remember, this project has 0 budget, no earnings, and I'm under 18, so funding isn't an option right now.

I also improved moderation after getting feedback from Harun, one of Crowdwide's moderators. Previously, moderators needed admin approval for almost EVERYTHING. That was my FAAAAAAAAAH system 😂 Now it's much smoother!

📊 Current Progress

  • 10 members
  • 37 posts
  • 4 communities

But there's a problem...

Users sign up, like posts, comment, and then disappear. They don't post or join communities! 😭

Only 2 of our 4 communities are getting consistent posts, and those are mostly from me.

A platform feels alive with 100–200 active users, not with 250 crore passive audience!

But Crowdwide has only 10 users... 🙄 BRO, I ROASTED MYSELF.

Today, our users will receive a newsletter, and I'm excited to test whether the recommendations actually match their interests.

And guess what? Crowdwide V2's release date will be announced soon! 👀

🌐 Try Crowdwide: https://www.crowdwide.run.place

💻 GitHub: https://github.com/DeveloperPuneet/Crowdwide

Got criticism? Roast it. FRY IT!! 🔥

And if you're on Crowdwide, PLEASE POST SOMETHING!! 😭😂

#crowdwide #buildinpublic #opensource #webdev

2 Comments 0 Replies with a post 0 0 Views 107
Join Crowdwide to like, comment, and share

Day 8 of Building Crowdwide!! 🚀😭

So today, Day 8 is completed, and I got 1 more new user and 1 more advertiser!! 🔥

📊 Current Stats

  • 10 members
  • 36 posts shared
  • 4 communities
  • 3 advertisers

AND NOW I'M GETTING THAT FULL-FULL VIBE!! 😭🙌

All the features I wanted to add are finally there! I added the Waves earning rules, explaining how many Waves you get for each activity.

We now have 20+ posts, and newsletters can include up to 20 posts/articles/polls!

No more empty feed looking like ewwwwwwww 💀😂 IT'S FILLED WITH POSTS NOW!!

📈 Time to Analyse!

Crowdwide's main goal is to give smaller communities and new users a fair chance.

So I'm collecting data and plotting graphs to analyse user behaviour and growth. This needs 8 weeks of data for a proper report.

Once it's ready, I'll share the results with NO SUGARCOATING. Good or bad, we'll see what the data says! 👀

🎉 What's Next?

  • All features added (for now 👀)
  • UI polished ✨
  • Weekly newsletters integrated 📩
  • Translation started working again... IDK HOWWWW 😭😂

API MOOD SWINGS FR!! 🙌

And once everything gets more polished...

CROWDWIDE V2?! 👀🔥

❤️ Wanna Try It?

Create an account, scroll through a few posts, and BOOOOM 💥 Your personalised newsletter arrives on Sunday!

We're also giving 25 Waves to initial users so they can explore Crowdwide and even start an advertising campaign!

🔗 Try Crowdwide: https://www.crowdwide.run.place

⭐ GitHub: https://github.com/DeveloperPuneet/Crowdwide

Need more Waves? Message me here!

THANK YOU SO MUCH FOR SUPPORTING CROWDWIDE!! ❤️🚀

#crowdwide #buildinpublic #opensource #webdev

1 Comments 0 Replies with a post 0 0 Views 68
Join Crowdwide to like, comment, and share

🚀 Day 7 of Building Crowdwide!

7 members, 35 posts, 4 communities, and 2 advertisers… we're still small, but we're moving forward! ❤️

This update covers a LOT:

🎉 My first external advertiser — and the unexpected problem I discovered when they couldn't launch their campaign because they didn't have enough Waves.

🌊 The Waves system — I gave 25 Waves to every current user account as a one-time early-user boost, and I'm working on making rewards, promotions, and transfers more transparent and abuse-resistant.

🛡️ Moderation updates — Harun has joined as a moderator and shared useful ideas about separating routine actions from actions that require admin approval. Welcome aboard, bro! 🤝

🎨 UI polishing — Crowdwide has 80+ pages, with around 30 or more still left to polish. BRO, WHY ARE THERE SO MANY PAGES? 😭

🌐 TRANSLATION IS BROKEN AGAIN!! — I tried different services, asked Claude for help, got it working temporarily, and then… it broke AGAIN. 💀 If you've worked with translation APIs, I could really use your help!

🎥 Future plans — I'm considering video tutorials to help new users and an idea called Crowdwide Spotlight for sharing external reviews.

I'm also working on improving the advertising experience, moderation tools, and the overall UI instead of endlessly adding more features.

Building with a budget of basically ZERO is an adventure. 😂 But we're still building, learning, fixing, and moving forward!

📖 Full details, stories, and updates here:

https://dev.to/puneetkumar2010/day-7-of-building…

#buildinpublic #crowdwide #webdev #programming

1 Comments 0 Replies with a post 0 0 Views 73
Join Crowdwide to like, comment, and share

🚀 Day 6 of Building Crowdwide — I Was Finally Done Adding Features

By Day 6, Crowdwide had reached a point where I was finally thinking:

Okay… I think I've added enough features. 😂

The biggest addition was Waves, Crowdwide's built-in platform currency.

Users could earn Waves through activity like likes, comments, communities, and quests. They could also use Waves to advertise their own products or projects without needing real money.

🌊 Building My Own Ad System

Instead of relying entirely on external advertising platforms, I built an advertising system directly into Crowdwide.

Advertisers could create campaigns, submit them for moderation, set budgets, and get approved before their ads went live.

I also wanted advertising to stay clean:

  • No gambling
  • No low-quality ads
  • No violent content
  • No spammy banners

The goal was to make advertising useful rather than simply filling the platform with ads.

🛠️ Time To Polish

By then, Crowdwide had a huge number of features: communities, chat, newsletters, search, Personal Recap, Community Radar, the Community Map, statistics, 2FA, Waves wallets, advertising, co-authoring, media tools, and much more.

I couldn't even remember everything I'd built. 😭

So instead of adding more, I decided to polish what already existed.

There were 70+ page templates and several email templates to clean up, along with responsive UI work and smaller improvements.

At the time, Crowdwide had:

  • 7 members
  • 25+ posts
  • 4 communities

And I was starting to realize that Crowdwide had become much bigger than the project I originally imagined.

A huge thanks also went to @harun9842245 for actually using Crowdwide, finding bugs, reporting them, and suggesting improvements.

That kind of feedback was incredibly valuable.

I wasn't building features anymore. I was starting to build the experience. 🚀

#Crowdwide #BuildInPublic

5 Comments 3 Replies with a post 0 0 Views 91
Join Crowdwide to like, comment, and share

🚀 Crowdwide Monetization Was Coming Together

Back then, Crowdwide was becoming more than a place where people simply posted and interacted.

I was working toward something bigger:

Communities that could actually grow. 🌊

A major part of that was the monetization and advertising system.

Communities meeting Crowdwide's requirements could eventually apply for monetization and enable advertising inside their communities.

The system included controls for:

  • Sponsored content and ad placements
  • Ad frequency
  • Campaign moderation
  • Impressions, clicks and CTR
  • Reporting and statistics

But the interesting part was Waves.

🌊 Waves

Crowdwide had an internal platform currency called Waves. They could be earned through activity and used for advertising campaigns.

The idea created a simple loop:

Participate → Earn Waves → Promote → Reach people → Grow

Advertisers could fund campaigns with Waves, while communities could potentially benefit from the activity and growth around them.

That connected:

Communities + Discovery + Advertising + Waves

🧠 The Bigger Idea

I didn't want Crowdwide to become another platform where only the biggest communities got attention.

A new community shouldn't need thousands of members before it has a chance to be discovered.

At the same time, advertising needed safeguards. Campaigns could be reviewed, moderated, suspended, or reported.

There was still plenty to build, especially around rewards, revenue sharing, anti-abuse systems, and testing.

But the foundation was there.

Crowdwide's monetization was finally starting to feel like a real system instead of just an idea. 🚀🌊

#Crowdwide #BuildInPublic

1 Comments 0 Replies with a post 0 0 Views 78
Join Crowdwide to like, comment, and share

🚀 Day 4 of Building Crowdwide — The Hard Part Isn't Building Features

On Day 4 of building Crowdwide, I was starting to realize that writing code wasn't necessarily the hardest part.

At the time, Crowdwide had:

  • 6 members
  • 20 posts
  • 3 communities

The numbers were still tiny, but they were enough to reveal something important.

🧠 Features Don't Automatically Create Users

I had already built things like hashtags, community posting, scheduled posts, quests, co-authoring, recaps, recommendations, and community discovery.

But then I looked at the usage...

Nobody was using half of them. 😭

That made me question something I had also experienced with my older project, Rizzzler.

You can build a feature, document it, explain it, and still have users completely ignore it.

So I started thinking beyond:

Idea → Code → Test → Done

A user also needs to discover the feature, understand it, see its value, and have a reason to return.

That's a completely different challenge.

💰 Giving Creators a Reason to Stay

I was also exploring partner-style monetization for Crowdwide.

I had contacted several companies, but there were no replies yet. 😭

The bigger idea wasn't simply putting ads everywhere.

I wanted to eventually create a system where creators and community owners could get something back for the effort they put into building communities and creating content.

Because if users are helping keep a platform alive, the platform should give them a reason to keep contributing.

I was still figuring out exactly how.

And honestly, that was becoming the real challenge.

Not:

"Can I build it?"

But:

"Can I give people a reason to use it, stay, and build something here?"

That was the question I was taking into Day 5. 🚀

#Crowdwide #BuildInPublic

1 Comments 0 Replies with a post 0 0 Views 70
Join Crowdwide to like, comment, and share

🚀 Day 3 of Building Crowdwide — Teaching Users a Feature Is Surprisingly Hard

Three days after launching Crowdwide, I learned something I hadn't expected:

Building a feature can be easier than getting users to actually use it.

At the time, Crowdwide had:

  • 6 members
  • 13 posts
  • 3 communities

The numbers were tiny, but having real users meant I could finally see how people interacted with what I built.

And I had seen this before.

Before Crowdwide, I built Rizzzler, a link-in-bio platform with a custom music feature. I documented it and even used it on my own page.

There were 10+ users, but only 2 were using custom music.

My first thought?

"I literally built this for you!" 😂

Crowdwide was teaching me the same lesson.

🗺️ Where Ideas Come From

Many of my features came from products I used or problems I experienced.

The Crowdwide community map, for example, was inspired by Obsidian's visual connections. I wondered:

> What if communities could have locations around the world? 🌍

So I built it.

At the time, my own community was basically the map's only resident. 😂

Crowdwide also had hashtags, community posting, scheduled posts, quests, co-authoring, recaps, and more.

But a feature existing doesn't mean users will discover it.

That's when I started thinking beyond:

Idea → Code → Test → Done

Users also need to discover, understand, and find value in a feature.

A feature nobody discovers is almost like a feature that doesn't exist.

So I wasn't just trying to build more.

I was learning how to build the path that leads users to what I'd already built. 🚀

And if someone actually discovered a hidden feature without me explaining it?

They deserved a chocolate. 😂🍫

#Crowdwide #BuildInPublic

1 Comments 0 Replies with a post 0 0 Views 65
Join Crowdwide to like, comment, and share

🚀 6 Members, 8 Posts, 3 Communities — And We Were Just Getting Started

Back then, Crowdwide was still tiny. Less than 48 hours after v1 launched, the numbers were:

  • 👥 6 members
  • 📝 8 posts
  • 🌍 3 communities

It wasn't a massive platform.

But honestly?

I was really happy to see those numbers. ❤️

Every member, every post, and every bit of feedback meant that someone was actually using something I had spent weeks building.

Around that time, @harun9842245 published a detailed review after testing Crowdwide for 48 hours. The review pointed out what worked, what broke, and what needed improvement.

I took that feedback seriously.

I started working on improvements almost immediately:

  • 🔎 Better search UI and search quality
  • 🐛 Multiple layout bug fixes
  • 💬 Fixed chat media loading issues
  • 🔗 Fixed invitation link problems
  • 💻 Improved code highlighting
  • 🔔 Fixed notification issues

That was one of the first moments where Crowdwide started feeling less like something I was building alone and more like an actual platform with people using it, testing it, and helping shape it.

The numbers were small.

6 members. 8 posts. 3 communities.

But every platform has to start somewhere.

And for Crowdwide, this was the beginning. 🚀

#Crowdwide #BuildInPublic #OpenSource #WebDev

1 Comments 0 Replies with a post 0 0 Views 68
Join Crowdwide to like, comment, and share

🚀 Crowdwide v1 Was Finally Here!

Back then, after weeks of building, breaking things, fixing them, fighting APIs, and battling free-tier limitations…

Crowdwide v1 was finally released. 😭🎉

The first stable version was live, with the core features I had been working toward: posts, articles, polls, communities, profiles, chat, media, reactions, bookmarks, notifications, and moderation tools.

But I didn't want Crowdwide to become just another social platform.

So I experimented with ideas that felt more unique:

  • 🗺️ Community Map — communities could have a visible presence on a map.
  • 🏆 Community Quests — communities could create challenges and reward winners with badges.
  • 🎧 Personal Recap — users could see summaries of their activity and interests.
  • ✍️ Co-authored Posts — multiple people could actually work together on one post.

There were also plenty of bugs. 😂 The map nearly drove me insane, APIs randomly caused problems, and something working locally absolutely did not guarantee it would work in production.

Translation was one of those problems too. It worked locally but still wasn't working properly after deployment.

Even after release, I knew v1 wasn't the final version. I wanted to keep improving the UI, infrastructure, translation, community tools, monetization, and more.

The biggest thing Crowdwide taught me was that building a platform isn't just writing code. It's testing, deploying, debugging weird production issues, researching alternatives, and doing it all again.

And then came the moment:

Crowdwide stopped being “a project I'm building” and became “a platform that's actually out there.” 🚀

That felt REALLY weird. 😂

#Crowdwide #WebDev #BuildInPublic #OpenSource

1 Comments 0 Replies with a post 0 0 Views 99
Join Crowdwide to like, comment, and share

🚀 Crowdwide Was Almost Ready — The Moment Before Release

Back then, Crowdwide was getting dangerously close to becoming a real product. After almost a month of building, I had planned to redeploy it on October 1st, 2026, with the stable release targeted for October 3rd.

The journey wasn’t exactly smooth. 😭

The server had been suspended because I was using free hosting, leaving Crowdwide offline for nearly a week. But during that time, I kept working.

I had added a lot:

  • Smarter feeds and discovery
  • Interest detection and advanced search
  • Hashtags, mentions, reactions, GIFs and emojis
  • Nested comments and sharing
  • Better chat and community moderation
  • Translation and writing suggestions
  • CAPTCHA, authentication and improved error handling
  • Responsive UI improvements
  • Stats, Help Center and data export

There was also a bigger idea behind it. Eventually, community owners could monetize their communities and share in ad revenue. But that would only make sense once real communities, users and activity existed.

Crowdwide was also another step in my cycle of learning → building → breaking things → building again. Vibeconnect had come before it, and some inspiration carried over, but Crowdwide was becoming its own thing.

And honestly, the biggest question was:

Would Crowdwide actually become a social platform used by real people — or would it just become another project sitting in my GitHub repo?

At that point, I was about to find out. 🚀

#Crowdwide #Programming #BuildInPublic

1 Comments 0 Replies with a post 0 0 Views 86
Join Crowdwide to like, comment, and share

🚀 I Was Building Crowdwide — A Social Platform Where Smaller Communities Get a Chance

Back when Crowdwide was still in its early stages, I realized I hadn't properly explained what the project was about.

At the time, Crowdwide had also become the KODA ONLINE FEST Season 2 Champion. 👑

🌐 What Was Crowdwide?

The idea was simple:

> Smaller communities should have a chance to grow without already being huge.

Large communities naturally had more visibility and momentum. A community starting with 10 people could easily struggle to get noticed.

I wanted to experiment with making being small not automatically mean being invisible.

🧩 What I Was Building

Crowdwide was becoming more than just a community platform:

  • 👥 Communities
  • 📝 Posts and articles
  • 💬 Group chats
  • 🛡️ Moderation
  • 👤 Profiles
  • 🔍 Discovery
  • 📈 Community growth
  • 🤖 Recommendation systems

🏗️ The Early Alpha

At that point, Crowdwide was very much an alpha. 😭

A lot of the UI and platform structure had been built, but authentication, backend systems, moderation, and other parts still needed work.

The deployment was mainly for testing and development.

🔐 Learning From Failure

Crowdwide wasn't my first social platform.

A previous project had barely survived a week. 😂

But that failure taught me a lot about security and the complexity of building social platforms.

I carried those lessons into Crowdwide.

🚀 The Experiment

The question I was trying to answer was:

> Can a social platform give smaller communities a real opportunity to be discovered?

I didn't know where Crowdwide would eventually end up.

But I wanted to find out.

Build → Break → Learn → Fix → Repeat.

#crowdwide #webdev #community #showdev #javascript

1 Comments 0 Replies with a post 0 0 Views 87
Join Crowdwide to like, comment, and share

🚀 Crowdwide Just Became a KODA Season 2 Champion 👑

Honestly, I didn't expect this at all.

Around 4–5 days earlier, I had hosted Crowdwide mainly for testing. I wasn't promoting it or thinking about entering any contest.

Then Harun (@harun9842245) found Crowdwide on DEV.to.

He became the first person to actually test it and reported some bugs. 😭 Some were expected because public account creation wasn't ready yet, and I was still using Postman to test backend requests.

Then Harun suggested:

> "You should submit Crowdwide to KODA ONLINE FEST."

So... I did.

🏆 And Then This Happened

I checked the results and opened the Hall of Champions.

And there it was:

👑 Crowdwide — S2 Champion

Crowdwide — Community & Social Platform

The description said:

> Build your community, grow it, manage it, and monetize it—with an algorithm that doesn’t let only the biggest communities win. 🚀

I genuinely just stared at the screen.

I WON. 😭🔥

A project I had only recently put online for testing had somehow become the KODA ONLINE FEST Season 2 Champion.

🛠️ But Crowdwide Wasn't Finished

Crowdwide was still a massive work in progress. Authentication, backend systems, testing, moderation, communities, monetization, and more still needed work.

So I didn't see this as the finish line.

I saw it as motivation to finish what I started.

👊 Thank You, Harun

If Harun hadn't tested Crowdwide and suggested KODA, I probably wouldn't have entered.

Thank you, Harun. 👊

Seeing a project still under development sitting in a Hall of Champions was honestly crazy.

There was still a lot to build.

Now back to cooking. 👨‍🍳🔥

#crowdwide #webdev #hackathon #showdev #buildinpublic

1 Comments 2 Replies with a post 0 0 Views 71
Join Crowdwide to like, comment, and share

From VibeConnect to CrowdWide

A while ago, I started building a social platform called VibeConnect. It was mainly a learning project where I experimented with authentication, posts, communities, profiles, and other social features.

But it had serious problems — weak security, incomplete media handling, missing features, and no proper 2FA.

Instead of endlessly patching it, I decided to start over.

That's how CrowdWide began.

Why CrowdWide?

While building and sharing projects, I noticed how difficult it can be for smaller creators and communities to get discovered. Established accounts already have momentum, while a new creator can spend weeks building something and barely get noticed.

So CrowdWide is built around communities, creators, and discovery — giving smaller communities an initial opportunity to be seen without guaranteeing popularity.

What I've Built

CrowdWide has grown far beyond the original idea.

  • Posts, articles, polls, drafts, scheduling and media uploads
  • Reactions, comments, bookmarks, sharing and threaded discussions
  • Public/private communities with roles, moderation and approval systems
  • Profiles, followers, privacy controls and saved posts
  • Personalized feeds, trending content, recommendations and search
  • RSS support and a posts API
  • TOTP 2FA, recovery codes, session management and rate limiting
  • Reports, moderation queues, audit logs and data export/deletion

I've also been experimenting with the feed algorithm, currently giving 40% of initial distribution to newer users/smaller communities, 55% to established communities, and 5% to trending content. It's an experiment, not a permanent rule.

What's Next

There are still plenty of things to finish: stronger automated testing, staging, monitoring, better spam detection, moderation improvements, API documentation, and more.

I'm building, breaking, fixing, and learning along the way.

That's where CrowdWide is today.

#crowdwide #buildinpublic #webdev #opensource #socialmedia

1 Comments 0 Replies with a post 0 0 Views 82
Join Crowdwide to like, comment, and share

🌟 Welcome to Crowdwide Spotlights!

Discover what makes Crowdwide worth exploring.

  • 🔎 Discover — Find people, communities & creators.
  • 🌟 Spotlight — Share something worth noticing.
  • 🚀 Support — Help rising communities get seen.
  • 💡 Explore — Find amazing content and projects.

Discover. Spotlight. Grow. 🚀

2 Comments 0 Replies with a post 0 0 Views 72
Join Crowdwide to like, comment, and share

Would You Choose a Giant Product… or a Fast-Moving Indie One?

This isn't a promotion.

I'm genuinely curious how developers think.

Imagine you have two platforms.

Platform A

  • Used by millions.
  • Around for years.
  • Stable and reliable.
  • Updates happen occasionally.
  • Your feature requests might never be seen.

Platform B

  • Built by a solo developer or small team.
  • Open source.
  • Modern technology.
  • New features ship quickly.
  • Bugs can get fixed within hours or days.
  • Your feedback can directly influence development.

Which one would you actually choose?

Not which one is more popular.

Which one would you enjoy using?

Something I've noticed while building projects is that new products don't just struggle to grow.

They struggle to get people to try them in the first place.

Most people naturally trust what they've used for years.

And honestly, that makes sense.

Why switch from something that already works?

But sometimes I wonder...

How many genuinely good products never get a chance simply because they launched yesterday instead of five years ago?

Imagine a platform that:

  • Ships meaningful updates every week.
  • Listens to community feedback.
  • Fixes important issues quickly.
  • Stays transparent about development.
  • Remains open source.

Would that make you more likely to try it?

Or would you still choose the established product because it already has the reputation?

I've been thinking about building around this philosophy.

A product where users actually influence what gets built.

Maybe it's a terrible idea.

Maybe it's exactly what some people want.

So I'm curious:

What would make you switch from a big, established platform to a new indie one?

Even if your answer is "Nothing would convince me." 😄

#discuss #buildinpublic #opensource #indiehacker #crowdwide

1 Comments 0 Replies with a post 0 0 Views 75
Join Crowdwide to like, comment, and share

I Built the Product. Then 7 Users Signed Up.

Not 7,000.

Not 700.

Just 7.

This is about an old project of mine called Rizzzler.
Live at https://www.rizzzler.work.gd
I built it while learning, spent countless hours improving the UI, adding features, fixing things, and trying to make the experience genuinely useful.

I even made it open source because I wanted people to see what I was building.

I wasn't backed by investors.
I didn't have a huge audience.
I built it with almost no budget, deploying as cheaply as possible and learning everything along the way.

And that's when I learned something nobody really tells you:

Building something good doesn't mean people will come.

After all that work...

7 people created an account.

The hardest part wasn't coding.

It was the silence after launching.

Not the bugs.
Not deployment.
Not debugging at 2 AM.

The silence.

I'm not posting this for sympathy.

I'm posting because I know many developers have experienced the same thing.

You build.
You polish.
You improve.
You launch.

Then you check the analytics...

Nothing.

So I'm asking for honest feedback.

  • What would stop you from using it?
  • What feels missing?
  • What should I have improved?
  • Would things like social login have made a difference?

I'd rather hear honest criticism than watch another day go by with zero users.

Maybe this reaches nobody.

Or maybe someone reading this becomes user #8.

Either way, I'll keep building. 🚀

#buildinpublic #opensource #indiehacker #webdevelopment #rizzzler

1 Comments 0 Replies with a post 0 0 Views 100
Join Crowdwide to like, comment, and share