stacktr.ee
By · Founder, Stacktree Last updated
Tester kit

One link for every test build.

Install steps for iPhone and Android, the codes to test with, and what is new in each build. After every build your agent rewrites the page at the same link, so testers open the newest build first.

Publish a tester kit free → See how it runs
No account for testers iPhone and Android on one page Same link every build
A tester kit at acme.northbank.studio/test-build moves from build 85 to build 87 at the same address. Your agent adds what is new since build 85 at the top and updates the iPhone and Android install cards. Then the owner sees that 6 of 8 testers have opened it since the update, each through their own named link.

Live Northbank Studio’s kit for the Acme Trips app. An example, retold from the kit we keep for our own testers.

How it runs

Your agent rewrites the kit. Testers keep the link.

The kit is one page: what is new, how to install it, what to test with. Your agent keeps it current after each build, and nobody has to send a new link.

01

After each build, your agent updates the kit.

It reads the commits since the last tester build and writes what changed in words testers understand. Then it updates the install steps and links, and the test accounts and codes.

fix: compass headingYour map arrow points the way you face. feat: offline docsTrip documents open with no signal. chore: bump SDKLeft out. Testers don’t need it.
02

The link testers have never changes.

Your agent calls update_site on the same page, so the link in their bookmarks, your team chat or the TestFlight notes still works. Each update keeps the version it replaced.

03

Testers see the newest build first.

The top of the page says what is new in this build, with the install steps right under it. Notes for older builds stay further down, for anyone who skipped one. On paid plans, a tester who opened the kit before also sees what changed since their last visit, marked on the page.

Why one page

Builds in a group chat vs one kit.

In a group chat

  • ×Links lost in threadsThe build link is somewhere in Slack, or in an email from two weeks ago.
  • דWhich build am I on?”Nobody can tell what changed since the one they tried, so they test the old thing again.
  • ×Test codes pasted aroundTrip codes and test logins sit in messages anyone can forward.

With one kit

  • ✓One link, every buildTesters bookmark it once. Your agent updates it in place after each build.
  • ✓What’s new at the topChanges since the last few builds, in plain words, with the install steps right under them.
  • ✓Codes behind a passcodeTesters type it once. Set the page to expire when the test round ends.
Every build kept

Each build’s kit is still there when the next one lands.

Each time your agent updates the kit, the version it replaced is kept: the last 5 on the free plan, the last 50 on paid plans. Restore any of them at the same link, from the page screen or by asking your agent.

Private by default

Test material stays with your testers.

Links are unguessable by default. Add what the test round needs.

A passcode

Testers type it once. Test accounts and codes stay behind it.

Any plan

An end date

Set the page to expire when the test round is over.

Any plan

A named link per tester

Each tester gets their own link, so you see who has opened the kit since the last update, by name.

Your own domain

Serve the kit from an address like test.yourstudio.com.

Stacktree hosts the page, not the app. The kit links out to wherever the build lives: TestFlight, your store’s internal testing track or your own file storage.

Set it up

One prompt, then a schedule.

Paste this into Claude Code in the app’s repo, with Stacktree connected. Fill in the app, the kit’s link and the last tester build.

Claude Code prompt
After each release build of <app>, update its tester kit on Stacktree (<kit link>).

1. Read the kit with get_site first, and keep its layout and anything written by hand.
2. Read the commits since the last tester build (build <N>).
3. Write a "New since build <N>" section at the top for testers: what changed, in words someone who never reads code understands. Leave out refactors and dependency bumps. Keep the earlier sections underneath, each headed "Also new since build <M>".
4. Update the build number, the version line on the iPhone and Android cards, the TestFlight and download links, and the test accounts and codes.
5. Call update_site on the same page, so the link testers have stays the same.

The trigger is your agent’s, not ours: a CI step after the release build, a Claude Code routine, or asking it when a build is ready. Each update keeps the version it replaced, so nothing is lost if one goes wrong.

S
Our testers have one link. Every build, the agent rewrites the top of the page from the commits and updates the install steps, and the link stays the same.
Steve Smith, who built Stacktree. How we use Stacktree →
FAQ

What people ask before they send one

Do testers need an account? +
No. They open the link in any browser, on the phone they test with. If the kit has a passcode they type it once. On iPhone they still need TestFlight, because that is how Apple delivers test builds.
Can I keep test codes private? +
Yes. Put a passcode on the kit, on any plan, and only people who have it can read the page and the codes on it. You can also set the page to expire when the test round ends.
Will notes from older builds disappear? +
No. Every update keeps the version it replaced: the last 5 on the free plan, the last 50 on paid plans. Your agent can list_versions and restore_version, or you can restore from the page screen, and the link stays the same. The prompt on this page also keeps earlier builds' notes on the page, under "Also new since build ...".
Can testers report problems on the page? +
Yes. Turn comments on and testers can tap anything on the page and leave a comment, from any browser or phone, with no login. Your agent reads them with list_feedback. If you already run an issue tracker, put its link in the kit and send reports there instead.
How do I know who has tested the new build? +
On paid plans, send each tester their own named link, and you see who has opened the kit since the last update, by name. An open is not the same as a test, so you can also ask testers to leave a comment once they have tried the build.
Can one page cover iPhone and Android? +
Yes. Put both install cards on the kit: the TestFlight steps for iPhone and the download link for Android. Testers open the same link on either phone and follow their own card.
Does Stacktree host the app itself? +
No. Stacktree hosts the page. The kit links out to wherever the build lives: TestFlight, your store's internal testing track or your own file storage.
Client project tracker Weekly work report Host a client demo site Password-protect a page Client spaces

Give your testers one link.

Testers never need an account. Free to start: a free page lasts 7 days, and up to 90 while testers keep opening it. Paid plans keep it for as long as the work runs.

Publish a tester kit free →