Does the button skip the password?

No. It opens the install page, which keeps the password, access codes, stop date, install cap and expiry.

Will a channel button update itself?

Yes. It shows the newest build's version within about 5 minutes of a new build going into the channel.

Can I use it on Free?

Yes, for build buttons. Free links expire after 7 days, so the button then leads to the expired page.

An install button for your test build, anywhere you write

Free and up for build buttons. Live channel buttons on Pro and Team

The test build link usually sits in a chat message that scrolls away. The places people actually look, a README, a Notion page, a wiki or the ticket under test, have no install button at all.

Every build page has "Add a download button": an "Install test build" badge, dark or light, with Markdown and HTML to paste. On Pro and Team a channel gets a live button that shows the version of the newest build and always opens it.

Start free See plans

Example

Download button

Build buttonInstall test build, dark, 200 x 60
Channel buttonInstall test build, v2.4.1 (119)
Views from the button42 of 310 page views this month

The badge says "test build" and never names the App Store or Google Play.

Made for

Open source and side projects with a GitHub README
Teams that keep QA notes in Notion, Confluence or Jira
Agencies with a project page per client

What it ends

Install links buried in chat history
A README that says "ask on Slack for the latest build"
Docs that point at a build from three releases ago

How it works

Step 1
Open the build or the channel
On the build page, or on the project's Testing page for a channel (Pro and Team), open the download button panel.
Step 2
Pick dark or light
Copy the Markdown or HTML. The alt text says "Install the test build of" your app name.
Step 3
Paste it
In a README, Notion, a wiki or a ticket. A tap opens the install page with its password, access codes and other controls kept.

Build buttons and channel buttons

A build button is a static image that links to that build's install page, on your custom domain when you have one. On Free the build link still expires after 7 days, and the button then leads to the expired page, so for a README that should keep working use a channel button.

A channel button (Pro and Team) is live: it shows "Install test build" over the version of the newest build in the channel, such as v2.4.1 (119), refreshed within 5 minutes. A testers only project shows "Invited testers" instead of the version, and a channel that is not active shows a grey "Link not active". No badge shows tester data.

From the CLI and AI tools

appforshare badge <id|slug|channel> prints the Markdown or HTML (--light for the light badge), so CI can update a README after an upload. Your AI coding assistant can fetch the same snippets with the read only MCP tool get_install_badge.

Links from the button carry ?ref=badge. On Pro and Team, analytics show how many page views came from a download button.

Good to know

It is a test build button, not an App Store or Google Play badge, and not a store listing.
Guest uploads have no dashboard, so no button.
The CLI command needs a Pro or Team token, like every CLI command.

Questions

Does the button skip the password?: No. It opens the install page, which keeps the password, access codes, stop date, install cap and expiry.
Will a channel button update itself?: Yes. It shows the newest build's version within about 5 minutes of a new build going into the channel.
Can I use it on Free?: Yes, for build buttons. Free links expire after 7 days, so the button then leads to the expired page.