Aisha
Free
Users seeking culturally grounded AI responses
Every 'offline AI assistant' you've tried still phones home for the model, the maps, or the voice layer — leaving you exposed the moment you cross a border, lose signal, or stop trusting the vendor's privacy policy. Eva runs the language model, speech recognition, text-to-speech, document search, maps, music, and Wikipedia lookup entirely on the Android device.
The home screen organizes work across four tabs — Chat, Images, Music, Docs — so you are not stitching together separate apps to get a grounded assistant plus media playback. Music continues in the background with lock-screen controls while you use the chat or docs tabs, which means the assistant does not interrupt your queue. The ceiling appears fast on older or mid-range hardware: on-device inference is bottlenecked by the ARM64 chip you have, not a server you can upgrade. No API is exposed, so there is no path to building a pipeline around Eva or connecting it to other tooling. The open-source repo has 1 star and 0 open issues at time of curation, meaning community support is effectively nonexistent.
Bottom line: Eva works exactly as described for a privacy-focused individual who wants a single offline Android app for chat, navigation, documents, and music — but teams building any kind of integration or needing consistent performance on budget hardware will hit hard walls with no workaround.
Find your fit
More options in Personal Assistants. Compare pricing, platforms, and features side by side.
Free
Users seeking culturally grounded AI responses
Freemium
Users of Claude, ChatGPT, or similar coding agents
Eva is a fully offline AI assistant for Android that bundles a chat interface grounded in local documents, on-device maps navigation, a music player with background playback, offline Wikipedia access, and a docs reader into a single APK. Nothing is transmitted off the device: no account creation, no cloud calls, no telemetry. The core workflow is tab-based — switch between Chat, Images, Music, and Docs — with the language model, speech recognition, and text-to-speech all resolved locally using the Cactus engine the repo ships with.
The differentiating detail is the depth of the offline stack. Most ‘offline’ apps offload at least one layer — voice, search, or the model itself — to a remote endpoint. Eva’s architecture, as described in the repo, keeps every component on the device: the language model runs via a bundled inference engine, document retrieval is local, and maps and Wikipedia are packaged for on-device use. The APK targets arm64-v8a, meaning the supported device pool is current-generation 64-bit Android hardware.
Eva fits one profile well: a privacy-focused individual on a capable Android device who wants a self-contained assistant with no accounts and no data leaving the phone. It breaks down in two directions. First, on-device inference performance is bounded by the phone’s chip — there is no fallback to a faster backend when the model is slow. Second, Eva exposes no API and has no integration surface, so it cannot be embedded in a workflow, connected to other tools, or automated. Teams evaluating it as a component in a larger system should look elsewhere; the tool is a standalone personal app, not a platform.
Sign in to rate this tool or suggest an edit.