Back to blog

How to ask for feedback on X as a developer (and get useful replies)

By Naod Tadele · · 5 min read

Loudcode guideAsk forfeedback on X

Most feedback posts on X look the same: a link, a screenshot and "would love any feedback!" Most of them get a few likes and no replies.

That isn't because people don't care. It's because the post asks for work without saying what work. Reading your landing page, trying your app and writing a thoughtful reply is a lot to ask from a stranger scrolling past. The fix is to make answering easy and specific.

This guide covers how to frame a feedback request, what to ask, example posts and what to do with the replies.

Ask one question, not "any feedback"

An open request makes the reader decide what to comment on. Most people skip that decision and scroll on. A narrow question removes it.

Compare these:

  • "Would love any feedback on my landing page."
  • "Does the headline on this page tell you what the product does? Yes or no is enough."

The second one can be answered in five seconds. That's the bar. If someone needs more than a minute to reply, expect far fewer replies.

Good feedback questions usually look like one of these:

  • Comprehension: "What do you think this does, from the screenshot alone?"
  • Choice: "A or B for the onboarding screen?"
  • Friction: "Where did you get stuck?" (only for people who already tried it)
  • Fit: "Would you use this for X, or do you already have something?"
  • Naming: "Which of these names would you remember tomorrow?"

A link alone asks people to leave X before they can help. Most won't. Put the thing you want feedback on inside the post.

  • For UI: a screenshot of the exact screen, cropped to the part you're asking about.
  • For copy: paste the text in the post.
  • For a flow: a short screen recording or two screenshots side by side.

Add the link in a reply or at the end for people who want to try it. The question should work without it.

Say who you want to hear from

"Feedback from anyone" invites drive by opinions. Naming the audience helps the right people recognize the post is for them, and gives everyone else permission to skip it.

  • "If you've been on call in the last year..."
  • "Backend devs who use Postgres daily..."
  • "If you've ever paid for a monitoring tool..."

You'll get fewer replies than from a vague post, but more of them will be useful.

Give context in one line

People give better feedback when they know where you are. One line is enough:

  • "Two weeks in, nobody has paid yet."
  • "About to launch, deciding on the pricing page."
  • "Rewriting onboarding because people drop off at step two."

Don't write a paragraph of backstory. Context should frame the question, not bury it.

Example posts

These are for Nightshift, a fictional tool that writes incident summaries for on-call engineers.

A comprehension check:

Example post
On-call engineers: from this screenshot alone, what do you think Nightshift does? Trying to see if the dashboard explains itself before I write any onboarding copy.

An A or B choice:

Example post
Two versions of the Nightshift summary email. A: timeline first. B: root cause first. If you've read a postmortem at 3am, which would you want? Just reply A or B.

Asking people who already tried it:

Example post
40 people signed up for the Nightshift beta last week. 11 created a summary. If you signed up and stopped, where did you lose interest? One word is plenty. No wrong answers.

A fit question:

Example post
Honest question for SREs: when an incident ends, who writes the summary on your team, and how long does it take? Building Nightshift for this and I want to know if I'm solving a real chore or an imagined one.

Notice none of these say "any feedback". Each one asks for something small and specific.

What to do with the replies

How you handle replies decides whether people help you again.

  1. Reply to everyone who answers. A short thanks is fine. Ask a follow up if the answer surprised you.
  2. Don't argue. If someone misread the screenshot, that is the feedback. Your page didn't explain it.
  3. Look for patterns, not votes. Three people stuck on the same step matters more than which option got more replies.
  4. Close the loop. When you ship a change because of the replies, post about it and say what changed.

The close the loop post is the one most developers skip, and it's often the most valuable. It shows people that replying to you leads somewhere, which makes the next request easier.

Example post
Last week I asked where people got stuck in Nightshift onboarding. Most of you said the Slack connect step. It's now optional and moved to the end. Setup is one screen shorter. Thanks to everyone who replied.

Mistakes to avoid

  • Asking for feedback on everything at once. Pick one screen, one sentence or one decision.
  • Only asking when you launch. Small questions during the build get more honest answers than a big launch post.
  • Fishing for compliments. "Is this cool?" gets polite replies. "What's confusing?" gets useful ones.
  • Defending every choice. If you already know the answer you want, don't ask.

How Loudcode helps

Loudcode reads your GitHub commits, pull requests and releases and drafts posts for X in your voice, including the follow up posts that close the loop when you ship something people asked for. On visual posts it can attach screenshots of your live app, so the screen you're asking about is in the post. If a quiet week leaves you without much to share, Ideas suggests posts to write, and you review every draft before it goes out. For more starting points, see 30 build in public post ideas.

You ship the code. We write the posts.

Your commits, revenue, traffic and a 30-second weekly check-in become build-in-public posts for X, in your voice. You approve every post.

Keep reading

All posts