I run a platform where indie developers or small startup can share pre-revenue services and get early users and feedback before turning them into real businesses.From Reddit, Indie Hackers, Hacker News, and even people around me, I can clearly see that many indie builders are building free tools and want to show them to others. Many also hope to turn them into businesses later. So I believe the...
A lot of builders underestimate how useful multilingual support can be.In the era of AI coding agents, adding basic i18n is much easier than it used to be. You can often just ask your coding agent to implement internationalization and list the languages you want. A typical starting set might be English, Spanish, Portuguese, French, German, Japanese, Korean, Chinese, Arabic, and Indonesian.One...
With vibe coding tools, adding multilingual support has become surprisingly easy. If you ask a model to add languages like Spanish, Portuguese, German, or French, it can usually set up the i18n structure pretty quickly, even for projects with a lot of text.One thing I’ve noticed is that once a site is indexed by Google, traffic doesn’t always come mainly from the US. Sometimes a significant...
When a lot of free or pre-revenue projects gather in one place, discovery tends to happen naturally. Otherwise, most directories just become SEO tools where builders drop their links and move on.
If you’re building something useful and want real feedback before adding pricing, feel free to participate. I wrote a bit more about why getting early users at this stage matters in the linked post.
I'm curious about projects that are launched and run for free.What are you building? How much does it cost you to operate? How long do you plan to keep it free?Do you have a monetization plan later, or is the goal something else (learning, community, portfolio, etc.)?Would love to hear about your projects and how you think about sustainability.
There seem to be two different philosophies about early monetization.One argues that you should start charging as soon as possible. Even getting a single paying user for a few dollars is considered a meaningful signal.The other approach is to first get exposure, gather feedback from real users, and only then plan monetization more carefully.I tend to lean toward the latter.If you're currently...
That said, I noticed you’ve put quite a bit of effort into blocking source view or browser inspection. I’d suggest reconsidering that. If everything truly runs in the browser, it would actually build more trust to let people verify that. Anyone can open the network tab and confirm that no data is being sent to a server.
I understand the concern about people copying your work. But realistically, with vibe coding, most of these tools can be rebuilt fairly quickly anyway. Trying to prevent copying at the browser level usually doesn’t add much protection.
Instead of focusing on blocking inspection, I’d suggest focusing on growing your user base and competing on quality. If you’re worried about code copying, lightweight obfuscation is probably a more practical solution than trying to disable developer tools.
I'm an early adopter. I genuinely enjoy exploring new ideas and trying early-stage products. But lately, when I browse launch platforms, even SideProject subreddit, it feels like almost everything is behind a paywall. Some offer a free trial, but I more often see posts saying something was vibe-coded in a few hours, and yet it costs over $50 to use. What feel odd to me is this: They are asking...