JevMade field notes / Architecture and workflow guide

Guide to building an AI assistant that controls Android phones

This guide explains how to connect an AI assistant to a real Android phone. It shows how the software looks at the screen, chooses actions, and avoids repeating mistakes.

Original by droidrunAgent workflows

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“mobile-jev” by droidrun. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Jev Mobile Agent contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

This project provides instructions and software for letting an AI assistant control a real Android phone. People use this to automate repetitive mobile tasks. It uses Jev, an AI tool that chooses from options rather than writing an answer.

The software looks at the phone screen and asks the AI tool to pick an action, like tapping. It records the chosen action immediately. If the connection fails, it will not try the same action again. This prevents the software from accidentally clicking a button twice.

This guide is useful for people testing automated mobile software. You need private access codes to use the required services. The AI claiming a task is finished is not proof of success. You must always check the actual phone to see if the changes happened.

Key takeaways

Always check the starting state of the phone before timing how long a task takes.
Record an action immediately so you have proof it happened even if the screen freezes.
Never let the software repeat an action if it is unsure if the first attempt worked.

More guides →See the experiments →