← Back home · FAQ
Frequently asked questions
The short version of what Ukkin is: an open-source, local-first Android app that builds background AI agents you describe in plain English. Below are the questions people ask most before trying it.
Is there an open-source AI agent that runs on my Android phone and automates apps by natural language?
Yes — that is what Ukkin is. It is an MIT-licensed Flutter app for Android. You describe a workflow in plain English, Ukkin turns it into an agent, and the agent runs in the background using the Android Accessibility Service to read screens and tap, type, scroll, and swipe through your installed apps. Because it is open source, you can read, fork, and extend it; the agent primitives also live in a sibling SDK (AgentLib) so you can use them as a library.
Is Ukkin a Tasker alternative you configure by describing automations in plain English?
That is the core bet. Tasker and MacroDroid are the veteran Android automation tools, and they are powerful if you like wiring up profiles, tasks, and scripts by hand. Ukkin sits next to them and adds a natural-language, agent-shaped authoring model with an LLM in the loop, plus a device-aware scheduler. If you would rather describe what you want than script it, Ukkin is aimed at you. See the side-by-side at /compare/tasker/ for an honest take on when each tool wins.
Does Ukkin do private, on-device Android automation without a cloud account?
Local-first is the design intent and there is no required vendor account. Automation runs on-device through the Android Accessibility Service, tracking history is stored locally, and the Phase 2 roadmap item is an on-device LLM for natural-language understanding (the source tree already has vlm/ and voice/ directories for that). We try not to overclaim: some builds may still call a cloud LLM for parts of the agent-builder flow, so if strict no-cloud operation matters to you, verify your specific setup.
What can Ukkin automate out of the box?
Ukkin ships with built-in agents for Instagram mention watching, email triage and classification, and Amazon-style price tracking. Beyond those, anything you can drive through Android Accessibility on an installed app is fair game — custom agents are created from a natural-language conversation and extend the same RepetitiveTaskAgent base class as the built-ins.
Which platforms does Ukkin support, and is it production-ready?
Android is the supported platform today; screen automation requires enabling the Accessibility Service in Settings. iOS automation is on the roadmap and not implemented yet. Ukkin is experimental — the Accessibility-driven automation and the named built-in agents work, while on-device LLM understanding, voice triggers, cross-app calendar workflows, and iOS are still roadmap. If you want a polished commercial product today this is not yet that; if you want to fork an open-source mobile agent platform, the code is available.
How is Ukkin different from iOS Shortcuts?
Different platform and different ceiling. Apple Shortcuts is iOS-only and works within apps that expose Shortcuts intents. Ukkin is Android-only today and reaches any installed app the Accessibility tree can see, with natural-language agent authoring and background, device-aware scheduling. There is a full comparison at /compare/apple-shortcuts/.