How to Find Open-Source Project Ideas That People Actually Want
Many developers build open-source projects that never gain traction. The biggest reason? They don’t validate demand before building. You don’t need a "marketing brain"—you just need to listen to real users, find pain points, and solve problems people care about.
This guide will show you where to find user complaints, how to analyze trends, and how to validate demand before coding.
1. Where to Find Communities Discussing Real Problems
Instead of guessing, observe where people discuss frustrations. Here are the best platforms:
👨💻 Developer-Focused Communities (Great for Open-Source & SaaS Ideas)
✅ GitHub Issues & Discussions – See what developers request in popular projects.
✅ Reddit (r/webdev, r/selfhosted, r/programming) – Developers discuss tools they need.
✅ Hacker News – See what’s trending in tech & software.
✅ Stack Overflow – Check recurring programming issues that lack good solutions.
✅ IndieHackers – Entrepreneurs share struggles with software, SaaS, and monetization.
🎯 Action Step: Search GitHub issues for "feature request" in your niche.
📢 Business & Productivity Communities (Great for SaaS & AI Automation Ideas)
✅ Product Hunt – Find new SaaS & AI tools before they explode.
✅ r/productivity & Zapier Forums – Professionals discuss automation & workflow pain points.
✅ G2 & Capterra Reviews – Read negative reviews of existing software to find gaps.
✅ r/SaaS & MicroAcquire – Find profitable but abandoned ideas.
🎯 Action Step: Read negative reviews on G2 and Capterra for "What do users complain about?".
🧠 AI & Machine Learning Communities (Great for AI-Based Products)
✅ Hugging Face Forums – See new AI model releases & use cases.
✅ r/MachineLearning (Reddit) – Find AI challenges & missing tools.
✅ Kaggle – Look at trending AI projects and gaps.
🎯 Action Step: Join Hugging Face Discord and ask, "What’s a common AI problem you face?".
2. How to Find & Validate Market Demand
🔍 Step 1: Search for User Complaints (Reddit, Quora, Twitter, Product Hunt)
- Go to Reddit, Quora, and Twitter and search:
"I wish there was a tool for…" or "I hate that I have to manually…" - If multiple users complain about the same issue, it’s a strong demand signal.
🎯 Example: Many Reddit users complain about long YouTube videos → AI summarization tools are needed.
📊 Step 2: Analyze Competitor Weaknesses (G2, Capterra, App Reviews)
- Check G2, Capterra, or App Store reviews of similar products.
- Look for negative reviews ("This tool is too slow!" or "I wish it had X feature.").
🎯 Example: Users hate that most YouTube summarizers require login → Create a login-free AI tool.
📢 Step 3: Talk to Real Users (Reddit, Discord, IndieHackers)
- Post: "Would you use an AI tool that does X?" on Reddit or Twitter.
- If 20+ people respond positively, that’s validation.
🎯 Example: IndieHackers founder asked about a GitHub automation tool → 100+ responses → Built a business around it.
💰 Step 4: Create a Simple Landing Page (Test Willingness to Pay)
- Create a simple page (Carrd, Notion, Framer) explaining your idea.
- Add a waitlist form ("Join Early Access").
- If people sign up, there’s demand.
🎯 Example: Someone pre-launched a Notion-based AI tool and got 300+ signups before writing code.
3. Best Validation Strategy: Combine Multiple Methods
✔ If you find:
✔ Reddit posts + negative reviews + real conversations + signups → 🚀 Build it!
✔ No strong demand? Pivot before wasting months coding.
🎯 Final Action Plan:
1️⃣ Pick a niche (e.g., AI, automation, developer tools).
2️⃣ Search user complaints (Reddit, Twitter, Quora, Product Hunt).
3️⃣ Read negative reviews (G2, App Store, Capterra).
4️⃣ Talk to real users (IndieHackers, Discord, Twitter).
5️⃣ Launch a waitlist & collect signups.
6️⃣ Build & iterate based on feedback.
Final Thoughts: Your Market Sense is a Skill, Not a Talent
- Even if you’re a developer with no marketing instincts, you can analyze real user problems.
- You don’t need to "guess" trends—just listen to what people already complain about.
- The best founders & open-source maintainers solve real problems, not just build cool tech.
🎯 Want Help Finding Your Next Open-Source Idea?
Let me know—I can search live Reddit & Twitter discussions to find real user problems for you! 🚀
Get in Touch with us
Related Posts
- Why Your Finance Team Spends 40% of Their Week on Work AI Can Now Do
- 用纯开源方案搭建生产级 SOC:Wazuh + DFIR-IRIS + 自研集成层实战记录
- How We Built a Real Security Operations Center With Open-Source Tools
- FarmScript:我们如何从零设计一门农业IoT领域特定语言
- FarmScript: How We Designed a Programming Language for Chanthaburi Durian Farmers
- 智慧农业项目为何止步于试点阶段
- Why Smart Farming Projects Fail Before They Leave the Pilot Stage
- ERP项目为何总是超支、延期,最终令人失望
- ERP Projects: Why They Cost More, Take Longer, and Disappoint More Than Expected
- AI Security in Production: What Enterprise Teams Must Know in 2026
- 弹性无人机蜂群设计:具备安全通信的无领导者容错网状网络
- Designing Resilient Drone Swarms: Leaderless-Tolerant Mesh Networks with Secure Communications
- NumPy广播规则详解:为什么`(3,)`和`(3,1)`行为不同——以及它何时会悄悄给出错误答案
- NumPy Broadcasting Rules: Why `(3,)` and `(3,1)` Behave Differently — and When It Silently Gives Wrong Answers
- 关键基础设施遭受攻击:从乌克兰电网战争看工业IT/OT安全
- Critical Infrastructure Under Fire: What IT/OT Security Teams Can Learn from Ukraine’s Energy Grid
- LM Studio代码开发的系统提示词工程:`temperature`、`context_length`与`stop`词详解
- LM Studio System Prompt Engineering for Code: `temperature`, `context_length`, and `stop` Tokens Explained
- LlamaIndex + pgvector: Production RAG for Thai and Japanese Business Documents
- simpliShop:专为泰国市场打造的按需定制多语言电商平台













