opensourceprojects.dev

A broadsheet for software that doesn't ask for your email

Self-hosted Appetize alternative that runs simulators in the browser
GitHub RepoViews193

Project Description

View on GitHub

Run iOS Simulators and Android Emulators in the Browser, On Your Own Macs

You've probably been there: a backend developer asks how to install the sandbox build, a PM wants to compare two versions side by side, or a designer needs to check a layout on a screen size they don't own. Every one of those requests lands on a mobile developer with a Mac and Xcode open. tapflow is a self-hosted answer to that problem — it puts iOS simulators and Android emulators in any browser, running on infrastructure you already control.

What It Does

tapflow describes itself as a self-hosted Appetize or BrowserStack alternative for mobile QA teams. The pitch is straightforward: your builds, streams, and recordings stay on your own machines instead of getting uploaded to a third-party cloud. Anyone on the team with a browser can then interact with the simulator rather than needing a Mac and a full mobile toolchain.

Architecturally, it connects three parts. There's a self-hosted relay (Linux or Mac) that also serves the dashboard on the same port, so you don't need a separate web server. There's a macOS agent that handles the actual simulator work. And there's the browser side, which streams over H.264 using a zero-buffer decoder — no MSE — with latency measurements documented in the repo. Notably, there's no WebDriverAgent involved, and setup is described as two lines. The project is MIT licensed, currently at v0.x and actively developed, with backward compatibility as the default and breaking changes flagged in the changelog.

Why It's Cool

  • The economics are the interesting part. Cloud simulator services charge recurring fees for remote devices while your own Macs can already run the same simulators. tapflow lets you reuse hardware you've already paid for, which changes the cost calculus for small teams.

  • Data stays home. If you're uneasy about uploading internal builds to a third-party service — and plenty of teams are — this sidesteps that entirely. Builds, streams, and recordings live on infrastructure you control.

  • No WebDriverAgent. That's called out prominently, and anyone who's fought with WDA setup will understand why it matters.

  • The dashboard rides on the relay's port. Skipping a separate web server is a small decision that removes a whole category of deployment friction.

  • The streaming approach is deliberate. A zero-buffer H.264 decoder without MSE suggests the team cares about latency enough to measure and document it rather than hand-wave. The repo includes a latency log if you want the numbers.

The README frames the problem honestly: it's not that physical devices or Xcode are bad, it's that access is uneven across a team. Designers, PMs, and backend developers shouldn't need to interrupt a mobile developer every time they want to see what shipped. tapflow's answer is to make the whole team's QA happen from a browser while the heavy lifting stays on hardware you own.

How to Try It

The project ships as a Docker image, which is the easiest path in. The README points to a quick-start guide, and setup instructions live in the environment-setup docs.

  1. Head to the repository: github.com/jo-duchan/tapflow
  2. Work through the Quick Start guide.
  3. Follow the environment setup docs for the relay and macOS agent configuration.
  4. If you want to see it before installing, there's a demo linked from the README.

The Docker image is available at tapflow/tapflow on Docker Hub. Full documentation lives at tapflow.dev. Since the project is pre-1.0, check the changelog before upgrading, though the maintainers say breaking changes are rare and always noted.

Final Thoughts

tapflow is aimed at a specific team shape: mobile QA groups with Macs already sitting around, who want browser-based access without shipping internal builds to someone else's cloud. If that's you, it's worth a look — the architecture is sensible, the licensing is permissive, and the project appears to be under active development with a published roadmap and changelog. It's early software at v0.x, so treat it accordingly, but the problem it targets is real and the approach is pragmatic. The fact that it's self-hosted and MIT-licensed means the worst case is you spend an afternoon evaluating it.


Follow @githubprojects for more developer tools and open source projects.

Back to Projects
Project ID: tapflowLast updated: November 16, 2026 at 02:48 AM