DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to test a running app by driving devices in the browser with Simfleet

Tap, swipe, and type on live iOS and Android screens from one browser wall.

Who it is forA mobile developer or QA tester who wants to watch and control several simulators and emulators from one screen while checking a build.

The problemSwitching between device windows and recording what each one shows makes multi-device checks slow to set up and easy to lose track of.

The outcomeEvery booted device streams into one browser view where the tester can click to tap, drag to swipe, and type, with lifecycle and deep-link controls in the inspector.

What you need first

  • A Mac running macOS
  • Bun 1.1 or newer (https://bun.sh)
  • Xcode for iOS work, plus `brew install mobai-app/tap/simslim baguette watchman`
  • Android SDK with platform-tools and emulator for Android work, plus `brew tap kdbhalala/avdslim https://github.com/kdbhalala/avdslim.git && brew install avdslim scrcpy`
  • A React Native or Expo app with a Git repository

Steps

  1. simfleet serve
  2. Open http://127.0.0.1:8790 in a browser.
  3. simfleet sim boot
  4. simfleet emu boot Pixel_8_API_35
  5. Click a device on the wall, then click to tap or drag to swipe.

Prompt for your agent

Using the simfleet repo (entropyconquers/simfleet), start `simfleet serve` in <path-to-app>, then open the dashboard at http://127.0.0.1:8790. Expected output: each booted simulator and emulator shown on the wall with its state. Verify that a tap sent from the dashboard changes the screen on the target device.

Caveat. The dashboard and API have no authentication and are reachable only on the local machine, so anyone with access to your user account can drive your devices.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page