From a7aceb1b8b5a92dd9f7c55e95a3292ce6eb9e07a Mon Sep 17 00:00:00 2001
From: Lana Begunova <70295997+lana-20@users.noreply.github.com>
Date: Thu, 1 Oct 2026 04:14:03 -0700
Subject: [PATCH 1/2] Mobile app automation, not native only: the app types
 Mobium drives

---
 docs/intro.md        | 10 +++++++---
 docusaurus.config.js |  2 +-
 2 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/docs/intro.md b/docs/intro.md
index f29b5c9..2b26a29 100644
--- a/docs/intro.md
+++ b/docs/intro.md
@@ -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.
 
@@ -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 React Native 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:
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 8e60918..032ac57 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -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: {

From 51b3bc0428e6ec60e0704608d8a7c16061bdc034 Mon Sep 17 00:00:00 2001
From: Lana Begunova <70295997+lana-20@users.noreply.github.com>
Date: Thu, 1 Oct 2026 05:14:15 -0700
Subject: [PATCH 2/2] Intro: cross-platform, not React Native, in the list of
 app types

---
 docs/intro.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/intro.md b/docs/intro.md
index 2b26a29..77212b9 100644
--- a/docs/intro.md
+++ b/docs/intro.md
@@ -22,7 +22,7 @@ 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, hybrid and React Native apps, and pages in a mobile browser
+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.