A vague requirement gets ignored. A clear one — even a hard one — gets a reply.
"Looking for a developer to build my app" gets scrolled past. "Looking for someone comfortable with React and Firebase to build a 3-screen MVP for a scheduling tool, aiming to launch in 6 weeks" gets a response.
The difference isn't effort. It's specificity. When people can't picture what success looks like, they can't picture themselves being the one who delivers it — so they move on.
If you're posting a requirement and it's not landing, before you assume the idea's the problem, check the clarity first. What does done actually look like? Who does it need? By when? Say that plainly, and the right person will recognize themselves in it.
1