How to share a side project and get useful feedback

Share a version that gives another person something concrete to understand or try. That might be a limited demo or a page with screenshots and a clear explanation of what works. State what is missing so people do not mistake a prototype for a complete service.

Decide what you want to learn before writing the page. Are people confused by the problem statement? Can they complete the main task? Does the result solve the problem you intended? One of these questions is enough for an initial request.

Use the project-page checklist to turn those decisions into a readable description and a usable demonstration.

Sign in and open Create a project. Enter the project URL and choose Mine if you made it. Creating the project starts a draft that you can prepare before publishing. If you are suggesting someone else’s work, choose Tipoff instead and keep attribution clear.

Complete the project information in the editor and use its publishing checks to resolve missing details. Publishing submits the project for approval. Until that review is complete, do not assume the project is visible in the public directory. You can return to your work through My Projects.

If you want to enter a competition, review its details and make that choice separately. Adding a project does not automatically enter it into a round, and acceptance into the directory does not guarantee a competition result.

“What do you think?” leaves the reviewer to choose the task. Instead, describe a short scenario and ask for observations: “Try finding an item near you. Where did you expect the location filter to be?”

Give people a realistic amount of work and tell them where to respond. Ask permission before turning a private response into a public testimonial or example. The useful-feedback guide includes a request template and a way to sort the responses.

After people respond, group the observations by the task they were trying to complete. Choose one change, explain the reason, and give people a route to try the revised version. If you decide against a suggestion, a brief explanation still closes the loop.

Project articles can record a change, an experiment, or a lesson. Keep the update specific: what was difficult, what changed, and what remains unresolved. Over time, that gives new visitors context that a screenshot alone cannot provide. If feedback reveals a task you cannot tackle alone, use the collaboration-brief guide to define an offer someone can respond to.