P1 — build the modern Compose Zara application shell on shared runtime state #197

New issue

Open

opened 2026-08-24 06:24:51 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-24 06:24:51 +00:00

(Migrated from github.com)

Parent: #194
Depends on: #171, #173, #195
Integrates with: #150, #151, #152, #159, #174-#177

Goal

Deliver a native Kotlin/Jetpack Compose/Material 3 application shell whose screens render the same typed authenticated runtime state used by Zara's assistant surface.

Required surfaces

Chat and Voice;
Tasks and Calendar;
SmartThings/devices and Integrations;
Settings;
assistant-role status;
server connection/authentication/reconnect;
diagnostics.

Requirements

Use the exact version pins and architecture selected by #195. Keep navigation, state restoration, accessibility, adaptive layout and lifecycle ownership native. The UI must not invent a parallel protocol, conversation store, task database, semantic state machine, or fake connected state.

At each exact GitHub candidate, CI must build an installable debug APK and upload it as a GitHub Actions artifact with the source commit recorded in application diagnostics.

Tests

TDD state rendering and actions for loading, connected, reconnecting, offline/degraded, permission denied, empty, partial data, error and restored-process states. Add Compose UI tests, accessibility assertions, navigation/state restoration, configuration change and process-death coverage.

Acceptance

Every required surface is navigable and backed by typed runtime models, and an installable APK is downloadable from the exact-head GitHub Actions run.

Parent: #194 Depends on: #171, #173, #195 Integrates with: #150, #151, #152, #159, #174-#177 ## Goal Deliver a native Kotlin/Jetpack Compose/Material 3 application shell whose screens render the same typed authenticated runtime state used by Zara's assistant surface. ## Required surfaces - Chat and Voice; - Tasks and Calendar; - SmartThings/devices and Integrations; - Settings; - assistant-role status; - server connection/authentication/reconnect; - diagnostics. ## Requirements Use the exact version pins and architecture selected by #195. Keep navigation, state restoration, accessibility, adaptive layout and lifecycle ownership native. The UI must not invent a parallel protocol, conversation store, task database, semantic state machine, or fake connected state. At each exact GitHub candidate, CI must build an installable debug APK and upload it as a GitHub Actions artifact with the source commit recorded in application diagnostics. ## Tests TDD state rendering and actions for loading, connected, reconnecting, offline/degraded, permission denied, empty, partial data, error and restored-process states. Add Compose UI tests, accessibility assertions, navigation/state restoration, configuration change and process-death coverage. ## Acceptance Every required surface is navigable and backed by typed runtime models, and an installable APK is downloadable from the exact-head GitHub Actions run.