docs: make Android native app the primary target

2026-07-09 03:50:27 +00:00
parent 2cd4730324
commit deec0c7fa3
6 changed files with 166 additions and 80 deletions
@@ -32,10 +32,12 @@ Secondary later:
   - Tool calls are first-class objects.

 2. Phone-native ergonomics
+   - Native Android app first, PWA fallback second.
   - Thumb-reachable controls.
   - Large tap targets.
   - Voice and upload actions always nearby.
   - Background task status survives app close/reopen.
+   - Haptics, native push, status bar/splash, and Android back behavior should be part of the product, not afterthoughts.

 3. Private by default
   - Self-hosted companion server.
@@ -243,8 +245,8 @@ The Settings health page should include a `Test Hermes` button.
 2. PWA push notification quirks.
   - Mitigation: support ntfy/Gotify fallback.

-3. Mobile browser audio quirks.
-   - Mitigation: test Android Chrome first; Capacitor later if needed.
+3. Mobile audio and lifecycle quirks.
+   - Mitigation: use Capacitor from the start; begin with WebView MediaRecorder and move to a native audio plugin if needed.

 4. Tool-call streaming requires Hermes integration changes.
   - Mitigation: companion adapter interface; use available callbacks in AIAgent where possible.