Getting Feedback Before You Publish

Why Feedback Matters

Before you connect your domain or share your tool publicly, it’s important to know:

• Does the tool solve the intended problem?

• Is the user experience smooth?

• Are there any confusing flows or bugs?

A quick round of feedback can save you hours of debugging and weeks of rework.

Who to Ask for Feedback

Start with:

• Teammates

• Existing users (if you’re replacing a manual process or old tool)

• A few trusted friends or clients who resemble your target users

They don’t need to be technical - they just need to use the tool like a real user would.

How to Share Your Tool (Before Going Live)

While your app is still in development (i.e. not published under a custom domain), you’ll get a preview URL hosted on fly.io.

This lets you:

• Open and use the live version of your app

• Share it with others to test

• Make edits in real-time using Kulp

What to Ask Testers to Do

Keep the feedback focused. Ask questions like:

• “Can you complete the main task without help?”

• “Is anything confusing or broken?”

• “What would you expect this button or screen to do?”

• “If this tool disappeared tomorrow, would you miss it?”

Ask them to use it naturally, not just skim it.

Collecting Feedback

Tools you can use:

• Simple Google Form

• WhatsApp or Slack messages

• Screen recordings (e.g., Loom or ZipMessage)

• In-app feedback widget (if you’ve added one)

Record their exact words, not just your interpretation.

Iterate Before You Publish

Once you’ve gathered feedback:

• Update your prompt or modify specific features

• Use “Fix the Issue” for quick changes

• Preview again and re-test

Don’t aim for perfect - just aim for clear, usable, and functional.

Then Go Live

Once your test users are satisfied and your app feels stable, you’re ready to publish.

Getting a second set of eyes is the fastest way to build something people actually want.