Get This Tool
Eva
Pricing
- Model
- Free
Summary
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.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Entire stack — language model, voice, maps, documents, Wikipedia — runs on-device with no network calls, so user data never reaches a third-party server even when the app is actively used.
- Open-source under a public GitHub repo with a downloadable APK, so you can audit the code, build from source, or self-host the distribution instead of depending on a vendor's continued operation.
- Background music playback with lock-screen controls persists while you use Chat or Docs tabs, so switching to ask a question does not interrupt the media session.
- Document-grounded chat runs locally, which means you can feed private files into the assistant without those documents ever leaving the device — a constraint that eliminates most cloud-based RAG tools from contention.
- No account creation or sign-in required, so there is no identity surface to compromise and no subscription to manage.
Cons
Sign in to edit- Inference speed is hard-capped by the phone's ARM64 chip — on mid-range or older Android hardware, response latency becomes unusable for anything beyond short queries, and there is no server fallback to compensate.
- No API, no webhook, no automation surface of any kind: Eva cannot be called from a script, integrated into a workflow, or connected to another tool. Any team that needs Eva's capabilities as a component rather than a standalone app will rebuild the functionality from scratch elsewhere.
- The repo shows 1 star and 0 contributors beyond the original author at time of curation — when something breaks on a specific Android version or model, there is no community to surface a fix or workaround.
- The APK targets arm64-v8a only, so devices outside that architecture are unsupported with no documented path to building for other targets.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Android
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-06-18T04:02:02.609Z
Best For
Who it's for
- Privacy-focused Android users
- Local media and knowledge management
- No-cloud personal assistance
What it does well
- Offline chat assistant with document grounding
- On-device maps navigation and routing
- Offline music player with genre sorting
- Offline Wikipedia and document reading
- Voice-activated personal assistant on Android
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Eva free?
- Yes — Eva is fully free to use. There is no paid tier.
- Is Eva open source?
- Yes. Eva is open source.
- Can I self-host Eva?
- Yes. Eva supports self-hosting on your own infrastructure.
- What platforms does Eva support?
- Eva is available on: Android.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
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.