You Are Building in a Void Until Someone Else Opens It

You have shipped. The app is live, the screenshots are done, the icon is fine. And you have no idea whether any of it is worth anything, because the only person who has ever used it is you.

That is the void. It is not a motivation problem or a marketing problem. It is an information problem: you cannot evaluate your own app, because you know what every button does, you never mistype anything, and you have never once opened it without knowing why you were there.

Everything you currently believe about your app is a guess wearing a confident expression.

---

Building got fast. Knowing did not.

This is newly acute. It is now genuinely possible to go from idea to shipped app in a weekend, and a lot of people are doing exactly that.

But the tooling only compressed one half of the loop. You can build in a weekend; you still cannot find out whether anyone wants it in a weekend. So the gap between "how fast I can ship" and "how fast I can learn" has never been wider — and the failure mode has shifted. It used to be I never finished. Now it is I finished four of these and none of them were wanted.

Shipping faster does not help if you are shipping faster into the same void.

---

What you cannot learn without users

Not opinions. Specific things, none of which you can get by staring at the code:

• Whether the first thirty seconds make sense. You cannot experience your own onboarding. You have never seen this app without knowing what it is.
• Which feature is actually the product. It is routinely not the one you spent the most time on. Sometimes it is a thing you nearly cut.
• Whether the problem is real. The most expensive discovery, and the one everyone postpones. Plenty of well-built apps solve a problem the author had and nobody else did.
• What breaks on hardware you do not own. Old devices, small screens, dark mode, a language you did not test.
• Whether anyone would ever pay. Different question from whether anyone likes it, and you cannot answer either one from the inside.

Every week you spend building without this is a week of decisions made on nothing.

---

Why promo codes are the shortest path

Your app has a price and no reputation. That is the hardest thing to sell there is — you are asking someone to pay money for an unknown quantity from an unknown developer.

A promo code removes the entire negotiation. There is no price objection, no refund risk, no "maybe later." You are asking someone to spend two minutes, not five dollars. That is a completely different ask, and the conversion difference is enormous.

You get 100 promo codes per version, per platform. It is not a big budget — but you do not need a big one. Twenty engaged users will tell you more than a thousand anonymous downloads. You are not buying scale here, you are buying information.

---

Free is the cheapest test you will ever run

Here is the part worth internalising, because it changes what you do next.

If people will not use it when it is free, they will certainly not pay for it. That sentence contains the whole argument for giving codes away before you have a paid funnel, a pricing page, or a marketing plan.

The signal is asymmetric, and both halves matter:

• Indifference at zero is conclusive. Twenty people take a free code, and nobody opens it twice. Nobody mentions it to anyone. Nobody replies to your email. That is a finished answer, and no amount of pricing work, copy rewriting, or ad spend fixes it. The problem is upstream of all of that.
• Enthusiasm at zero is encouraging but not proof. People using and sharing something free tells you the thing is wanted. It does not tell you it is worth money. Willingness to pay is a separate question, and plenty of products are loved at $0 and ignored at $5.

So free is a filter, not a verdict. It cannot confirm you have a business. It can very cheaply confirm you do not — and it does that in a week, for nothing, before you have spent three months building a subscription flow for an app nobody would have subscribed to.

The mistake is running that test after you have built the paywall, the pricing page, the onboarding funnel, and the launch plan. At that point the sunk cost is doing your thinking for you.

Watch for the behaviours you cannot fake: did they open it more than once? Did anyone tell someone else without being asked? Did anyone come back after a week? Did anyone ask when the next version lands? Those are worth more than any survey response, because nobody is being polite when they do them.

---

Getting information, not just installs

This is where most giveaways fail. Codes go out, installs happen, and nothing is learned. To close the loop, three things have to be true:

A real person has to get the code. A scraper that redeems in four seconds teaches you nothing. This is the actual argument for bot protection — not fairness, information. A code held by a bot is a code you cannot learn from.

You need to know who has it. Anonymous redemptions are a dead end. Capture the email at claim time or you have no way back to the person.

You have to ask a specific question. This is the part everyone skips. "Any feedback?" gets silence. Ask one narrow question and you get answers:

• "What did you expect to happen when you first opened it?"
• "What is the first thing you would change?"
• "Was there a moment you nearly gave up?"

Send it about a week after they claim: long enough to have used it, soon enough to remember. Expect a small reply rate and be pleased with it, because five real answers is a roadmap.

You do not need special tooling for this. Once you have the addresses they are yours to use — export the list, or sync it into whatever you already send email with, and run it as a plain reply-to-me email or a two-question survey. A short personal note from the person who built the thing outperforms a formal survey almost every time, so do not overthink the format.

---

What to do with what you hear

Two rules that make this worth the effort.

Weight actions over opinions. "This looks great!" is politeness. "I opened it twice and could not work out where my data went" is gold. Watch what people did, not what they say they think.

Look for the repeat. One person disliking your colour scheme is noise. Three people independently confusing the same screen is a bug in your thinking, and it is the single most valuable output of the whole exercise.

Then ship the fix, and tell the people who told you. That is how a giveaway list turns into an audience rather than a spreadsheet of strangers.

---

The honest framing

A code giveaway will not make your app popular. A hundred codes is not a growth strategy, it will not move you up a chart, and — since people who redeem promo codes cannot rate or review — it will not affect your rating either.

What it does is end the void. It converts a set of confident guesses into a short list of things you now actually know, which is the input to every decision you make next.

Ship, then find out. The order matters, and most people stop after the first half.

---

Promo Code Queue gets your codes into real hands from one link — one per person, bots kept out — and keeps the email address of everyone who shows up, including the people who arrive after the codes run out. That list is who you ask.