App and offline
OpenACAI works in the browser today and is being kept ready for Android and iOS. This page explains what can be installed, what works offline, and which features stay web-only until privacy and safety controls are finished.
Install
Add OpenACAI to this device.
Use the install button when this browser offers it. Otherwise, use the browser menu and choose the add-to-home-screen or install option.
Checking whether this browser can install OpenACAI.
On phones and tablets, open the browser menu and look for Add to Home Screen, Install App, or Add to Dock. OpenACAI still works normally if that option is not shown.
Readiness
What is ready right now.
The same public contracts used by the monitor and API are summarized here so visitors, partners, and future app clients get the same answer.
The public website is the active installable path where browsers support Add to Home Screen.
62 public documents are listed for future clients, with 0 required missing.
22 public routes can be treated as offline-safe by the PWA and future apps.
8 app-facing public data areas are mapped for package-validated startup with sync schema 1.4.
Android and iOS submissions are not being represented as live until privacy, support, and safety gates pass.
Native apps should keep public web fallback visible until app-store readiness is true.
Contact, account, staff, partner, and case-file flows stay network-only and no-store.
Forms can be prepared on the page
The Forms Library gives visitors official source links plus local editable worksheets, print packets, and plain steps without submitting private answers.
Resources can be searched and saved locally
Public resource data is exported as JSON and CSV for the website, partners, and future apps. Private messages and searches are not analytics payloads.
GAMHON starts with safe web games
Current games are small, keyboard-friendly, no-audio activities for breathing, grounding, mood checks, connection prompts, and shared-screen cooperation.
Profiles exist without public exposure
Signed-in users can save GAMHON preferences and export a safer profile card. Public profiles, messages, rooms, and friend graphs remain gated.
Accessibility settings are public and local
Visitors can use larger text, high contrast, reduced motion, keyboard controls, screen-reader structure, and printable workflows.
Crisis paths stay visible
Emergency and 988 guidance must remain reachable. Offline clients should warn about stale data instead of hiding crisis and safety links.
What can stay available
The future app has a public data map now.
The sync map tells a browser or future native app what public material can be kept for speed and offline use, and what must stay private or online-only.
The public service list, review details, search data, and saved-list IDs can stay available after a successful load.
Official form links, plain explanations, and worksheet prompts can load without sending private answers anywhere.
Print, copy, and local prep packets can be updated as public templates while drafts stay on the device.
Food, benefits, housing, utilities, technology, and safety guide data can be kept for quick reopening.
Short planning paths can remain usable offline, with crisis and contact actions treated carefully.
Low-pressure activity metadata can be cached; names, messages, health details, and social graphs are not part of it.
Partner and professional reference links can be shipped as public citation metadata.
Apps can validate a draft locally, but submission stays on the no-store web contact path.
Public app contracts
Stable URLs for future Android and iOS builds.
These documents are public by design. They contain route maps, cache rules, offline package data, data-safety boundaries, and store-readiness notes without secrets or private case data.
How to install the current web app
On supported browsers, use the browser menu or address-bar install prompt to add OpenACAI to the home screen. The website still works normally if the browser does not show an install option.
What can work offline
- Public help pages
- Resource and forms reference data after a successful load
- Some GAMHON activities and local progress
- Accessibility preferences stored on the device
- The offline fallback page
What should stay online only
- Contact submissions
- Account sign-in and profile saves
- Staff and partner portals
- Private help requests
- Case files or document uploads
- Donation processors
Social sign-in boundary
Social sign-in should connect through provider credentials and server-side configuration, not theme files. Until Google, Microsoft, Discord, or other provider keys are configured and reviewed, the site shows account access without pretending those providers are live.
Offline privacy rule
Public reference data may be cached. Private contact text, profile notes, account sessions, uploaded files, case details, and analytics identifiers should not be cached in the public offline bundle.
Continuity and cache source
Public cache behavior is documented in openacai-cache-policy.json and continuity behavior is documented in openacai-continuity.json.
Public pages can be cached for speed. Contact and account routes are kept no-store so private support details do not become offline content.