Skip to content

Mobile app automation: the app types Mobium drives #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lana-20 merged 2 commits into from
Oct 1, 2026
Merged

Mobile app automation: the app types Mobium drives #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a7aceb1
Mobile app automation, not native only: the app types Mobium drives
lana-20 Oct 1, 2026
51b3bc0
Intro: cross-platform, not React Native, in the list of app types
lana-20 Oct 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions docs/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@
title: Introduction
slug: /
sidebar_position: 0
description: Native app automation for AI agents and humans — Android emulators and phones, iOS simulators and iPhones, from one Go binary.
description: Mobile app automation for AI agents and humans — Android emulators and phones, iOS simulators and iPhones, from one Go binary.
---

# Mobium

*Mutatis mutandis.*

**Native app automation for AI agents and humans.** Android emulators,
**Mobile app automation for AI agents and humans.** Android emulators,
Android phones, iOS simulators and iPhones, driven through one tool layer
from a single Go binary with no runtime dependencies.

Expand All @@ -22,10 +22,14 @@ that changed a login screen should be able to open the app, read what is
actually on screen, tap through the flow and look at the result — without a
person driving an emulator for it. People get the same commands.

It drives native apps the way [Vibium](https://github.com/VibiumDev/vibium)
It drives native, hybrid and cross-platform apps, and pages in a mobile browser
or installed as a PWA, the way [Vibium](https://github.com/VibiumDev/vibium)
drives browsers: a `map` → `@ref` → act loop that an agent can follow
without learning a new model.

What each app type needs, and which apps of each type were driven, is in
[APP-TYPES](https://github.com/mobiumdev/mobium/blob/main/docs/APP-TYPES.md).

## The loop

`map` reads the screen and gives everything a person could act on a ref:
Expand Down
2 changes: 1 addition & 1 deletion docusaurus.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ import {themes as prismThemes} from 'prism-react-renderer';
/** @type {import('@docusaurus/types').Config} */
const config = {
title: 'Mobium',
tagline: 'Native app automation for AI agents and humans',
tagline: 'Mobile app automation for AI agents and humans',
favicon: 'img/favicon.svg',

future: {
Expand Down
Loading