HOW IT WORKS

Ship Your First App Today

AppShare gives mobile app developer teams a complete build distribution workflow: create an app, upload a release, decide who's allowed to access it, and track every install and piece of feedback that comes back, without losing version history, tester context, or access control along the way.

Before You Start

Everything You'll Manage Along the Way

Before your first upload, it helps to know what each part of AppShare is actually for. These are the four things most teams touch on every release.

Quick Releases

Not every build needs a full app entry first. Quick Release lets you upload a one-off .apk or .ipa, add an optional expiry or password, and get an install link back immediately, no extra setup.

UDID Manager

A UDID is the unique identifier tied to one iOS device. It works like a shared library: testers add their own device's UDID, and developers encode allowance for those devices into the build.

Tester Management

Every app keeps its own tester list, built by inviting people individually or in groups. Lists stay separate per app, so a client's testers and an internal QA group never end up mixed together.

Password Protection

A release's install page can stay fully public, or sit behind a password you set in release settings, useful for a pre-release build or a client demo you'd rather keep contained for now.

WHOLE CYCLE

One Continuous Release Workflow

These six steps aren't separate tools you jump between. They're one workflow, and each one leads straight into the next.

STEP 1

Create an Application

Every release starts with an app record. Set it up once, and every future build, tester list, and public page for this app builds on top of it, without getting mixed up with your other projects.

App Name

Up to 24 characters, shown right on the public install page, so testers know what they're looking at.

Shareable Link

Choose a Unique URL, generated fresh each release, or a Persistent URL that stays the same over time.

App Stage & Alerts

Set the app's current stage and configure alert settings before the very first build even lands.

Dashboard Upload

Drag in an .apk or .ipa, up to 2GB, straight from your desktop, no other steps needed.

CLI Upload

Push a build from your terminal using your app's App ID, no dashboard trip required at all.

CI/CD Upload

Trigger an upload automatically from GitHub Actions, GitLab CI/CD, Bitrise, Jenkins, or others.

STEP 2

Upload Your Build

A build reaches AppShare from wherever your team already works: the dashboard, a terminal, or a pipeline. Every upload path ends up in the same place, one release, ready to configure.

Step 03

Configure Release Settings

Before anyone gets a link, decide what they're allowed to do with it. Release settings covers who can access the build, how long it stays live, and what context they see before installing.

Public or Private

Keep the release open to anyone with the link, or lock it behind a password.

Expiry Date

Set how long the release stays installable, so an old build doesn't quietly stay live.

Release Notes

Add a short note on what changed, and a Change Log entry for anything with more detail.

Page Link

A public page with build details, ready to open in any browser, no app needed.

Install Link

A direct link that triggers the install itself, one tap and it's underway.

QR Code

Scan-to-install, for anyone testing from a physical device in the room.

Page Customization

Add your logo, favicon, color theme, or a custom domain, your call on layout.

Step 04

Install Page Is Created

The moment release settings are saved, AppShare generates a dedicated install page for that build, ready to share however works best for whoever's on the other end.

Step 05

Others Install and Give Feedback

From here, it's out of your hands until someone installs it. Testers open the page, install the build, and can post directly into that release's forum if something needs flagging.

No Store Account Needed

Testers install straight from the link, no App Store or Play Store account needed at all.

Device Registration (iOS)

For an ad hoc build, only devices whose UDID was added and encoded into that build can install.

Release Forum

Testers and your team post comments and attachments directly on that release, tied to the exact build.

Unique URL

Every release gets its own link automatically, generated fresh and never reused for the next one.

Persistent URL

One custom-slug link covers the app's entire release history, so testers only need one bookmark.

Show Old Releases

Toggle older releases visible or hidden on the public page, so testers can reach a past version.

Step 06

Push New Builds

A release rarely stays static. When it's time for the next version, you decide whether testers land on a brand new link each time, or the same one, updated in place.

Notifications

Get Notified as the Workflow Moves

A release doesn't stop mattering once the link goes out. AppShare can keep your team in the loop as things happen, across the channels you already check.

See All Integrations

FAQ

Questions About the Release Workflow

How do I create my first app on AppShare?

Start a new app, give it a name up to 24 characters, and set its shareable link as either a Unique URL or a Persistent URL. AppShare generates an install page automatically once your first build is uploaded.

Can I upload a build from the command line?

Yes. The AppShare CLI lets you push builds using your App ID, without opening the dashboard.

What's the difference between a Unique URL and a Persistent URL?

A Unique URL is generated automatically for each release and can't be customized. A Persistent URL uses a custom slug and stays the same across future releases.

How does the UDID Manager work?

You or your testers add each iOS device's UDID and model to the list once. AppShare checks a build's install attempt against that list, so only registered devices can complete an ad hoc install.