BlogProduct

The PostEngage Android App Is in Closed Beta, and It Needs Twelve People

The phone app is built. Google will not let it onto the Play Store until twelve people have tested it for fourteen days, which is why this post exists.

The PostEngage team4 min read

The app is finished enough to use and cannot be published. Those two facts are not in tension, they are just how Google Play works now, and the gap between them is filled by twelve people we have not found yet.

Here is the rule, in Google's words rather than ours. An app published from a personal developer account has to run a closed test with at least twelve testers who stay opted in for fourteen consecutive days before it is eligible for production. Not twelve installs. Twelve accounts, continuously, for two weeks. Miss a day, or drop to eleven, and the fourteen days start again.

So this is not a launch post. It is a request, and it is worth being plain about which one you are reading.

What the app actually is

The same account, on your phone. It is not a companion, a notifier, or a stripped viewer.

  1. Automations. Create, edit, pause and dry-run a rule. The same builder, laid out for a thumb.
  2. The inbox. Conversations across the account, with automated and human replies in one thread.
  3. Leads. Open a lead, move its stage, add a tag, capture an email, write a note.
  4. Held replies. The queue of drafts a guard stopped, with the reason next to each one. This is the screen we most wanted on a phone, because a held reply is a decision and decisions happen away from a desk.
  5. Activity. What ran, what sent, what was refused.

If you have used PostEngage in a browser, there is nothing new to learn. That was the point.

What it is not

It does not post. It does not schedule. It has no analytics beyond the four numbers on the Overview, because we deleted the analytics surface rather than port a screen that reported nothing real.

It also does not replace the browser for setting things up the first time. Connecting an Instagram account goes through Meta's OAuth flow, and that flow is genuinely nicer on a laptop. Everything after the connection is better on the phone.

What testing actually asks of you

Less than it sounds, and more than nothing.

You install the app from a link we email you, you sign in with the account you already have, and you leave it installed for fourteen days. That is the whole requirement. You do not have to open it daily, file reports, or fill in a survey. If you use it and something is wrong, tell us — but the fourteen days are about staying opted in, not about activity.

The one thing that does not work is joining and leaving. If you install it, decide it is not for you and uninstall on day three, the counter drops and everybody else's fourteen days reset with it. So the honest ask is: join if you actually intend to keep it.

Why we are asking rather than buying

There are services that sell twelve testers. They cost about what you would expect and the accounts are exactly as real as that price implies.

We are not using them, for a reason that is about us rather than about ethics in the abstract. A test group assembled to satisfy a counter produces a passing test and no information. Twelve people who use PostEngage on a real Instagram account for two weeks produce a list of things that are wrong on a phone, which is the only reason to run a beta at all.

How to join

If you have an account, it is one click: Settings → What's next → Ask for a spot. It uses the email you signed up with, so there is nothing to type.

If you do not have an account yet, the beta page takes an email address directly. You do not need to be a customer to test it, though it will be a quieter fourteen days if you have no Instagram account connected.

Either way we email you Google's opt-in link when a spot opens. The list is read by a person, not a queue, and it is short.

What happens after the fourteen days

Production review, then the Play Store listing, then a normal release. Everyone in the closed test keeps the app; there is no migration and nothing to reinstall.

If we do not find twelve people, the app stays where it is — built, working, and unpublishable. That is the actual stake.

We could have written this as a launch announcement and left the requirement out. The requirement is the entire reason the post exists, though, and a launch post that is secretly a favour is a worse thing to read than a favour.

One email when we publish.

No drip sequence, no “quick question” follow-up. Unsubscribe is one click and we honour it immediately.