Where to share something you built

Prepare a small package people can use

Write a plain sentence about what the project does, who it helps and what someone can try. Include the live URL, one useful image or short recording, the creator’s name and the intended device. Mention meaningful limitations such as desktop-only controls or an account requirement before the click surprises someone.

Create a specific project page rather than sharing a generic homepage when possible. That page should contain the working link, a concise explanation, accurate sharing metadata and a route to the creator’s other work. Keep an answer ready for “Why did you build it?” and “What kind of feedback would help?” Avoid asking only for attention.

Match the place to the kind of work

The following list suggests audience fit, not guaranteed acceptance or distribution. Check the current page and rules before submitting. A directory can curate selectively, and a community may require participation beyond posting your own links.

Scroll to see all columns →

• Clipcade ↗
• ExplainerTools creators ↗
• itch.io publishing ↗
• Product Hunt launch guide ↗
• Show HN rules ↗
• Replit community ↗

Read the rules and use the right format

Show HN has a specific purpose: something the maker worked on that people can meaningfully try. Its rules distinguish that from blog posts, lists, newsletters and signup-only pages. If you are sharing an article rather than a usable project, choose the appropriate normal submission route instead of forcing it into Show HN.

On Reddit, read the actual community’s rules, pinned posts and self-promotion expectations. State that you made the project. Do not ask friends for coordinated votes or paste the same launch text into unrelated communities. On curated directories, an accurate submission is an invitation to review, not a promise of inclusion.

Replit’s public community is a possible route, but verify the current controls in your account before relying on a profile feature. A published app URL is the safer concrete link.

Write for the people in that place

For an educational community, lead with the idea the tool makes easier to understand. For game developers, describe an interesting mechanic or technical choice. For potential users, show the task and result. You can adapt the emphasis while keeping the facts consistent. Do not invent different capabilities to fit each audience.

Draft three short introductions for this real project: an interactive map that compares walking time from a chosen point. Audiences: local urbanism community, technical builder community and my own creator profile. Include what a person can try, disclose that I made it, state that travel times are estimates, and ask one useful feedback question. Do not invent users, endorsements, accuracy guarantees or mobile support. Remind me to check each community’s current rules before posting.

Treat sharing as the start of a conversation

After posting, be available to answer questions and fix broken links. Record useful feedback and separate requests from bugs. If someone says they could not use the tool on a phone, reproduce that path instead of debating the wording. Update the project page when a limitation changes.

Measure more than clicks. Use a tagged link where appropriate, then compare visits with the useful action in the product. A large referral spike with no completed tasks may mean a mismatch, unclear setup or a broken experience. Keep a simple log of where you shared, what audience you expected and what you learned before repeating the launch elsewhere.