Key takeaways
- Say what you need and an AI agent works your apps and the web until it is done, on a hidden background screen.
- No per-app integration: it reads the screen the way a person does, so it is not limited to a list of supported apps.
- There is no Mika server. Your requests and screen go only to the model provider you set up.
- It hands logins, verification codes and payments back to you, and by default checks before spending money.
- The catches: phone control needs a wireless debugging pairing, and automating apps may break their terms of service.
What it is
Mika describes itself as an AI assistant on your phone: you say what you need, and it works your apps and the web until it is done. It is free, released under the Apache-2.0 licence, and the code is public on GitHub under the name Mika.
The problem it solves
Phone chores that span several apps are slow to do by hand, and most automation tools need a specific integration for each app. Mika takes a different route: it looks at the screen and finds buttons the way a person does, with no app APIs and no per-app integration.
It does this on a hidden background screen, so you can keep using your phone while it works.
What you get
- Hands-off errands: the agent taps, types and scrolls in other apps while your own screen stays free.
- Control: you can jump in or stop a task at any time, and schedules and conditions are supported.
- Web tasks too: in the built-in browser you can say what you want on the page you are reading.
- Sensible limits: logins, verification codes and payments are handed to you, and by default it checks only before spending money.
- Less exposure: there is no Mika server, and API keys and memories are stored encrypted on the phone.
The catches
- Permissions: to operate phone apps you must pair wireless debugging on the phone once. Android turns it off when you change Wi-Fi or restart, and some phone systems leave it out.
- Platform limits: chat, web and files need Android 11 or later, operating apps needs Android 12 or later with Android 14 or newer recommended, and the Linux sandbox needs arm64 devices. The project offers a compatibility self-check for doubtful phones.
- Privacy: what you say and what is on your screen go to the model provider you choose, so that provider's terms matter.
- Rules and gaps: operating third-party apps automatically may break their terms of service. Payment and password pages block screenshots, and the built-in app knowledge is written in Chinese.
What we did not test
We did not install Mika, pair a phone, connect a model or run any task. We cannot say how reliable it is across real apps, or how it behaves on any given phone. Every claim here comes from a literal quote in the project's README or the GitHub API, and the feature descriptions are the project's own.
Verdict
Editors' view: this is aimed at Android users comfortable with developer settings who want an agent to handle multi-app chores, and who are happy to choose and pay for their own model provider. If you are wary of giving software control of your accounts, start with chat and web tasks only, and keep important tasks supervised.
Sources
Need help adopting this, or have a software project in mind?
Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.
Start a conversation →