Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

tapflow

tapflow• Pinned

tapflow: Self-hosted browser access to iOS simulators and Android emulators for team-based mobile QA.

What problem it solves

Mobile QA access is uneven across teams: non-developers often depend on a mobile developer to install sandbox builds, compare behavior, or check layouts across screen sizes. Traditional local tooling requires each teammate to have a Mac and a complete mobile toolchain, while cloud simulator services require uploading internal builds to a third party.

Key features

  • Browser-based simulator streaming — QA users can select an available iOS simulator or Android emulator and interact with it in real time from a browser. Streams support codec negotiation and fall back to JPEG when hardware or WASM decoding is unavailable.

    Source: README

  • Self-hosted infrastructure — A relay hosts the dashboard, accounts, builds, streams, and session recordings on infrastructure controlled by the team. Agents make outbound connections to the relay, avoiding inbound firewall rules.

    Source: README

  • Interactive device control — The dashboard forwards touch, swipe, pinch, keyboard, clipboard, and device audio interactions. It also provides deeplink controls, network toggling, screenshots, and shareable session recordings.

    Source: README

  • Build and team management — Teams can upload application packages, track build status, invite members, assign dashboard roles, and issue scoped Personal Access Tokens. REST endpoints support CI/CD and AI-agent workflows.

    Source: README

  • Automation interfaces — An experimental flow runner replays YAML flows with conditional waits and JUnit reports without invoking an LLM during replay. An experimental MCP server exposes simulator control to LLM agents.

    Source: README

Quick start

Copied verbatim from the project's README.

npm install -g tapflow
# or: yarn global add tapflow  |  pnpm add -g tapflow
tapflow setup
tapflow start
# ✓ Relay started on http://localhost:4000
# ✓ iOS Agent connected (3 simulators available)

Who it may suit

This may suit mobile QA teams that need shared simulator access without requiring every tester to install a native mobile toolchain. It may also suit developers, product managers, and designers who need to inspect application behavior through a browser.

Topics to discuss

  • Which self-hosting topology works best for teams with separate relay and agent hosts?

  • Which QA workflows most need deterministic flow replay or screenshot API support?

  • What security and operational practices should teams adopt before exposing a shared relay beyond the local network?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/jo-duchan/tapflow#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/jo-duchan/tapflow

Comments

…