Crowdwide Is Now Public for Testing 🚀
So yeah... Crowdwide is finally public. I've been working on it for more than 15 days before the first deployment, and after a lot of debugging, fixing things, breaking things again, and dealing with some really annoying email errors, I finally got it to a point where I can let other people use it. The first public deployment was on September 9, 2026 at 11:13 AM (New Delhi time). But it's still a…
Crowdwide, a social platform for creating communities, has officially gone public for testing. The creator, who has been working on the platform for over 15 days, launched the first public deployment on September 9, 2026, at 11:13 AM (New Delhi time). Despite being a test version, Crowdwide allows users to create communities for various purposes such as posts, articles, polls, comments, media, moderation, roles, guidelines, and more.
The main concept behind Crowdwide is to enable users to build a community around a specific topic or interest rather than having a single profile and feed. The platform aims to experiment with providing around 35-40% visibility to newer users and community content in the feed, while the remaining portion can include established communities, other content, and existing popular posts. However, this visibility distribution is not fixed and will be evaluated during the testing phase.
The primary goal of Crowdwide's public test is to gather feedback and real-world usage from actual users. The creator is encouraging people to create communities, join existing ones, post content, write articles, create polls, comment, moderate communities, and try out different features. The tester's role is crucial in identifying potential bugs and areas for improvement. Any issues encountered during this test will provide valuable insights for the platform's future development.
The public testing of Crowdwide is scheduled to continue until September 30, 2026. During this period, the creator will focus on fixing bugs reported by users, improving the email system and its user interface, refining the website interface, enhancing the write-ups and information on the website, providing accurate platform statistics, optimizing the site performance, adding GIFs to comments and direct messages, extending storage clusters, and improving the site's responsiveness on various devices.
While the site is already responsive, there is always room for improvement. One of the significant challenges faced during the development process was the email system, which initially had verification issues. The creator spent considerable time troubleshooting the email setup and ensuring its proper functionality.
Monetization is not currently a focus of Crowdwide. The creator plans to concentrate on making the platform robust and user-friendly before exploring monetization options. Monetization strategies, such as providing monetization for communities and creators, may be considered later if the platform gains enough traction and user engagement.
It is essential to note that the current version of Crowdwide is a test version, and the data generated during the public testing phase will not be retained permanently. On September 30, the platform will reset the database, and a stable version will be published. Therefore, any accounts, communities, or content created during the test phase will be deleted after September 30.
The creator encourages users to visit https://www.crowdwide.run.place/ and https://github.com/DeveloperPuneet/Crowdwide to explore the platform, create communities, post content, and provide feedback. The creator specifically requests users to report any bugs or issues they encounter, as these will be invaluable in shaping the future of Crowdwide.
The creator emphasizes that finding bugs is currently more important than receiving compliments during this testing phase. The public testing of Crowdwide has officially begun, and the creator is eager to see how users interact with the platform moving forward.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
