Vision AI step by step
Capture images, annotate them, train a detection model (Colab or on your PC), then test it live, all from the Vision AI screen.
Last reviewed 2 November 2026
By the end of this page you will have trained a first model that recognises an object of your choice on your phone screen, and you will have seen it working live. ⏱ 30 minutes of hands-on work, plus training time (a few minutes to over an hour depending on the machine).
Before you start
- A license that includes Vision AI: that means the Pro plan or above (see License, plans and account). Without it the buttons on the page are greyed out.
- A connected device showing Free on the Dashboard.
- Know which object you want recognised (a button, an icon, a character...).
What is a detection model?
A detection model is a small program that looks at an image and answers: "there is a play button here, a monster there". Nobody codes it by hand: it learns by example.
You show it dozens of images where you drew a rectangle and a name (the class) around the object yourself. Training means letting the computer find what those examples have in common. Then, given a new image, the model draws a box around what it recognises and gives a confidence percentage.
AppsMobs uses models from the YOLO family. You do not need to know them: the app walks you through 5 steps, shown at the top of the Vision AI screen.
What Vision AI cannot do yet inside your scripts
The YOLO functions you can call from scripts are being reworked: do not build anything important on them yet. The steps below (capture, annotate, train, test) work in the Vision AI screen. To act on an image inside a script, use the image functions (find_image, tap_image).
How many images do you need?
Everyone asks this first. The honest answer is: it depends, and the numbers below are only indicative.
- The app suggests aiming for 50 to 100 examples per class for a first attempt.
- Variety matters more than quantity: different maps, times, zoom levels. Ten near-identical images are worth about one.
- Keep a few images with nothing to detect, so the model learns not to see the object everywhere.
- If the test (step 5) misses cases, add images of those exact cases and train again. You iterate; you do not guess the right number on the first go.
The 5 steps
- 1
Open Vision AI and pick your device
Click Vision AI in the sidebar. You are on step 1 Capture, Live screen view.
In the right-hand panel, open the System section and choose your phone from the device list. If the list is empty, click the refresh button next to it.
1Step 1 Capture2Device choice (System section)3Start the preview4Step 3 Images5Step 4 Train6Step 5 Test You are done when your phone appears in the list.
- 2
Name your project and start the preview
In Current Project, type a project name (for example
my-game). One project = one game or one goal. Everything is stored inDocuments\AppsMobs\VisionProjects.Click Start the preview (mark 3 above). The phone screen appears on the left, live. You can also press Alt + Shift + S to come back to this Live screen view.
- 3
Capture varied images
Play normally on the phone, or set the screen to the situation you want. For each situation, click the 📷 button in the toolbar (it captures the screen to annotate later). The ⭐ button next to it starts automatic captures: you set the frequency and the duration.
Change situation between captures: another map, another moment, another zoom. The counter on the 3 Images tab goes up with each image you keep.
- 4
Annotate: draw around the object (step 2)
Click 2 Annotate. Create a class with + New Class and give it a short, clear name (
play_button,monster). Select the rectangle tool (the first icon of the image toolbar), then draw a tight rectangle around the object.- A half-hidden object still gets a box, on its visible part.
- Several objects in one image: one rectangle each.
- A box that is too wide teaches the model that the background is part of the object.
Save with Ctrl + S and move to the next image. The number next to 2 Annotate counts your annotations.
- 5
Check and sort your images (step 3)
Click 3 Images (or See my images). Filter by class, or show only images without boxes. Open an image to fix its boxes, and move between images with ← →.
Delete blurry images, duplicates and bad captures: a clean dataset beats a big one.
- 6
Prepare the dataset and train (step 4)
Click 4 Train. The panel starts with Generate Dataset:
- Source Images: keep All project, or pick only the validated images.
- Split: three boxes Train / Valid / Test. Keep 70 / 20 / 10 (the total must be 100 %).
- Optional: the Pre-processing and Augmentation options (flip, rotation, noise, blur) create variants of your images.
- Click Generate Version. The app shows an Estimated number of resulting images.
Then choose where to train (next section) and click Train. A progress bar follows the run. At the end, the model is a
.ptfile. - 7
Test your model live (step 5)
Click 5 Test. In Trained Models, choose your model (or Browse for a
.ptfile on your disk, for instance the one you brought back from Colab), then Load.Set the Confidence Threshold: the higher it is, the fewer false detections, but the more objects the model lets through. Start the preview: boxes with a percentage appear on the live screen.
You are done when your object is boxed on screen. If not, go back to steps 1 and 2 to add images of the missed cases, then train again.
Colab or on your PC?
In step 4 Train, the Train YOLO section offers two routes.
Title in the app: Cloud GPU (free). This is Google Colab with a T4 graphics card: the app announces about 15 to 60 minutes, at no cost to you.
- Click Colab. AppsMobs exports your dataset as a ZIP file and shows an instructions window with its location (an "open the export folder" button).
- Click Open Google Colab: the Colab page opens in your browser. You need a Google account.
- In Colab, upload your ZIP, then run Runtime → Run all.
- When it finishes, download the
.ptfile and load it in step 5 Test with Browse.
Upside: no graphics card needed, nothing to install. Downside: a Google account and a round trip of files.
Title in the app: Local (GPU required). Training runs on your PC.
Settings (the defaults are fine to start with):
| Field | What it does | Default |
|---|---|---|
| Epochs | Number of passes over your images | 50 |
| Batch | Images processed at once (lower it if memory runs out) | 16 |
| Img | Training image size | 640 |
| Device | Graphics card number | 0 |
| Model | yolov8n (nano, fast), yolov8s (small), yolov8m (medium, heavier) | yolov8n |
For a first try: yolov8n, 50 epochs, size 640. Click Train; the stop button (red square) interrupts.
You need an NVIDIA graphics card for this to be fast. Without one, use Colab.
Missing module
If local training needs a Python library that is absent, a Missing module message appears with an Install button. Click it and wait for Installed!. See also Troubleshooting.
And reinforcement?
Next to the 5 steps, the Advanced area holds Reinforcement and Agent settings. This is reinforcement learning: an agent learns by trying actions. It is slow (often hours) and reserved for the Ultimate plan. Always start with a detection model.
What is limited
Good to know
- COCO / Pascal VOC export: the buttons exist but are marked "Coming Soon". Today the format used is YOLO's.
- Modal (another online training service) is greyed out: "Coming Soon".
- YOLO functions in scripts are being reworked (see above).
- Training does not replace a well-written script: if a fixed image is enough to recognise your button,
tap_imageis simpler.
It does not work?
| Message or symptom | Cause | Fix |
|---|---|---|
| Greyed-out buttons | The license does not include Vision AI | Move to Pro or above (plans) |
| "No live screen yet" | The preview is not started | Pick the device, then Start the preview |
| "Définissez un nom de projet" (shown in French) | The project name is empty | Fill in the name in Current Project |
| "Total != 100%" | Train / Valid / Test do not add up to 100 | Adjust the three boxes |
| "Missing module" | A Python library is missing locally | Click Install, or use Colab |
| The model misses objects | Not enough variety | Add images of those cases and train again |
| The model sees objects everywhere | Too few empty images, or threshold too low | Add empty images, raise the Confidence Threshold |
All error messages are gathered in Troubleshooting.
What next
- Write a Python script to use what you taught the app to detect.
- Scheduling with Automation to run your script by itself.
- Troubleshooting if something blocks.