---
title: "Comment by DemoVexa on \"Launching an App Is Nothing Like Building One\" | Hashnode"
description: "I'm at a similar stage with my own product, so here's my answer to your question. Launch posts mostly reach other builders. The people who become users are usua"
url: "https://hashnode.com/posts/launching-an-app-is-nothing-like-building-one/6af0d3cc7a0e27a4ed02c366/comment/6af2870466cdd033d94c34ec"
---

[Discussion](https://hashnode.com/posts/launching-an-app-is-nothing-like-building-one/6af0d3cc7a0e27a4ed02c366)

Comment [Launching an App Is Nothing Like Building One](https://hashnode.com/posts/launching-an-app-is-nothing-like-building-one/6af0d3cc7a0e27a4ed02c366)

[DemoVexa](https://hashnode.com/@demovexa)

[1d ago](https://hashnode.com/posts/launching-an-app-is-nothing-like-building-one/6af0d3cc7a0e27a4ed02c366/comment/6af2870466cdd033d94c34ec)

I'm at a similar stage with my own product, so here's my answer to your question. Launch posts mostly reach other builders. The people who become users are usually in places where they're already asking about the problem, so answering those questions well, and mentioning the app only when it truly fits, tends to do more than an announcement. What I wish I'd known earlier is that family testers are kind. Watching them use it beats asking what they think. Pick the one task a new visitor should finish in the first few minutes, sit next to someone trying it, and stay quiet. Where they pause is usually the next thing to fix. Launch day as a starting line is spot on.