git404hub

what is mobai-ci fr?

mobai-app/mobai-ci — explained in plain English

Analysis updated 2026-05-18

0ShellAudience · developerComplexity · 3/5Setup · moderate

tl;dr

A CLI that runs scripted mobile app UI tests in CI, on free simulators/emulators or paid real devices.

vibe map

mindmap
  root((mobai-ci))
    What it does
      Runs .mob or Maestro flows
      Screenshots on failure
      JUnit reports
    Tech stack
      Shell
      GitHub Actions
    Use cases
      iOS simulator testing
      Android emulator testing
      Cloud device farm runs
    Audience
      Mobile developers
      QA engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Run mobile UI test flows automatically on every GitHub Actions push

VIBE 2

Test an iOS app on a free simulator booted directly on the CI runner

VIBE 3

Test an Android app on a free emulator booted directly on the CI runner

VIBE 4

Run the same flows against real devices in BrowserStack or Sauce Labs

what's the stack?

ShellGitHub ActionsMaestro

how it stacks up fr

mobai-app/mobai-ci123satyajeet123/bitnet-serveradeilsonrbrito/cross-model-consult
Stars000
LanguageShellShellShell
Setup difficultymoderateeasymoderate
Complexity3/52/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Free tier covers on-runner simulators/emulators only, cloud device farms and BYOD need a paid MobAI account key.

in plain english

mobai-ci is a command line tool for running automated tests on mobile apps as part of a continuous integration pipeline, meaning the checks that run automatically every time code is pushed to a repository. It plays back short scripted sequences of taps, swipes, and checks called flows against a real or simulated phone screen, then produces a report that shows what happened, including a screenshot and a snapshot of the screen layout for any step that failed, so a developer can see why a test broke rather than just that it did. There are four ways to get a device to run these flows against. Two are free: an iOS simulator booted directly on a macOS build runner, and an Android emulator booted on a Linux build runner. Two require a paid MobAI account: running the flows on a real device hosted in a cloud device farm service like BrowserStack, Sauce Labs, or AWS Device Farm, or running them against a physical device connected to your own computer over a network tunnel while the automation itself runs elsewhere. Flows are written as short text files, either in MobAI's own simple format or in the format used by an existing tool called Maestro, which mobai-ci also understands, so teams that already have Maestro flows do not need to rewrite them. A flow describes steps like launching the app fresh, waiting for a piece of text to appear on screen, tapping it, and taking a screenshot. Flows can also accept parameters, so the same flow can be pointed at a staging environment or a production environment without editing the file. The tool installs as a GitHub Action for teams using GitHub Actions, or as a plain shell script install for any other environment, and it supports macOS and Linux on both Intel and Arm processors. The project includes ready-made example workflow files for each of the four device paths, covering iOS simulator, Android emulator, cloud device farm, and bring-your-own-device setups.

prompts (copy fr)

prompt 1
Help me set up mobai-ci as a GitHub Action to test my iOS app on a simulator
prompt 2
Write a .mob flow that launches my app and taps through an onboarding screen
prompt 3
Explain how to run my existing Maestro flows through mobai-ci without rewriting them
prompt 4
Show me how to parameterize a mobai-ci flow to run against staging and production

Frequently asked questions

what is mobai-ci fr?

A CLI that runs scripted mobile app UI tests in CI, on free simulators/emulators or paid real devices.

What language is mobai-ci written in?

Mainly Shell. The stack also includes Shell, GitHub Actions, Maestro.

How hard is mobai-ci to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is mobai-ci for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.