product
Ark is an offline-first survival computer for mobile. It should remain useful when the network disappears after initial setup: maps, navigation, knowledge packs, secure notes and documents, local AI/RAG, cached feeds, weather context, and practical sensor tools.
- Prepared civilians who want a phone-based offline command center before travel, storms, grid outages, or remote work.
- Field users who need fast access to maps, saved places, checklists, guides, notes, and local search without trusting a live connection.
- Privacy-conscious users who expect personal notes, documents, chats, locations, and backups to stay local and understandable.
- Offline truth first: every critical status should say what works offline, what still needs a download, and what is online-only.
- Survival-grade calm: serious, direct, and utilitarian. Avoid playful camping language and technical implementation detail unless the user is in diagnostics.
- One action per moment: when a screen is crowded, promote the frequent action and group the rest behind a predictable menu or sheet.
- Plain-language readiness: describe outcomes, not engine names. Prefer "Navigation ready" over "Valhalla graph loaded" outside diagnostics.
- Local control: downloads, indexing, backup, and model work must expose progress, failure recovery, and restart paths.
- Security clarity: if vault protection only gates some data, the UI and docs must say so. If a surface contains sensitive user data, prefer vault-aware access.
- Not a playful camping app.
- Not a technical demo of native modules.
- Not a cloud dashboard.
- Not a dense debug console for normal users.
Short, calm, operational. Use concrete status labels and recovery actions. Avoid hype, cute phrasing, and unexplained model/runtime names in primary UI.