Preview links for every client, every project, every revision

Agencies don't have a build-sharing problem — they have a dozen of them at once. PreviewAPK gives every build of every client app its own permanent preview link: clients open it in the browser, your team stops scheduling demo calls, and revisions never get mixed up.

Kill the demo-call tax

The standard way to show a client a build is a ceremony: find a slot across two companies' calendars, get everyone on a video call, share a screen, drive an emulator while eight people squint at a compressed video feed — and reschedule the whole thing when the client contact who approves budgets can't make it. Multiply that by every project and every revision, and senior people are spending billable hours on logistics instead of feedback.

A preview link removes the ceremony. The project manager drops the build's link into the status email or the shared Slack channel. The client opens it at 9pm in their timezone, taps through the actual app on a real Android device in the cloud, and replies against that specific build. If a live walkthrough is genuinely needed, one person drives the session and the client watches the same session in their browser — still no installs, no screen-share troubleshooting, no "sorry, my VPN blocks that."

Separate clients, separate links

Each app lives on its own device in your portal, with a stable, view-only preview link. That structure does two jobs at once:

• Clients stay separate. You send each client only their own builds' links. A link opens one build of one app — there's no shared folder, no attachment thread, and no path from one client's preview to another's.
• Revisions stay straight. The link sent in week 2 still opens week 2's build in week 6. "Approved" has a fixed referent: when a client signs off, both sides can reopen the exact build that was signed off, compare it against the current revision, and settle "that's not what we approved" conversations with evidence instead of memory.

It also ends the APK-attachment sprawl — the app-release.apk files accumulating in inboxes and shared drives, none of them labeled well enough to know which client, let alone which revision, they belong to.

Pricing that maps to your project list

PreviewAPK is $19/month per device with unlimited testing. For an agency, per-device pricing is the useful shape: dedicate a device to a client project and swap its builds as the work evolves, so the preview cost of every engagement is known before you quote it — small enough to absorb, clean enough to pass through as a line item.

Unlimited matters on the agency side, too. Account managers demo builds repeatedly; clients revisit links days after you send them; stakeholders you never met — a founder, someone from marketing, someone from legal — open the link and watch. With no minute meters and no per-seat math, none of that activity needs monitoring, and no demo ever ends because a usage cap did.

Real-phone sign-off, when a client asks

Some clients want final acceptance on their own hardware. Each device can include a QR code and an APK download for installing on a real phone — off by default, enabled per device by you. The client scans the code and installs the exact build they already reviewed in the browser, so the sign-off pass and the review pass are the same artifact.

FAQ

How do agencies keep different clients' builds separate?

Each client's app gets its own device in your PreviewAPK portal. You send each client only their own session's link — it opens the build live while the session runs, and links only ever watch: driving happens in your portal, never from a link.

Do clients need an account or an install to view a build?

No. A preview link opens in any browser with the app already installed and running on a cloud device. One person drives; everyone else watches live. Viewers install nothing.

How does pricing work across several client projects?

$19 per month per device with unlimited testing and no minute meters. Each client project maps to an app, so preview costs are predictable per project and easy to pass through or absorb.

Can a client install a build on their own phone for sign-off?

Yes, when you enable it. Each device has an optional QR code and APK download for real-phone installs; it's off by default and controlled per device.

Keep going

• For client approvals — builds clients review without sideloading.
• For QA testers — device and version coverage without a device lab.
• For freelance developers — deliver builds clients actually open.