6.0 KiB
UI/UX review: chat Back latency and save feedback
User requested another navigation/animation/feedback review, specifically chat Back taking several seconds. No production chats/runs or personal devices used.
| Finding | Change/source | Focused verification | Landing | Delivery |
|---|---|---|---|---|
| Unchanged answer parts reparsed/rebuilt during streaming | da44001a caches each Markdown render subtree until text or inherited appearance changes; link callbacks remain current |
Deterministic reuse regression failed before fix; text/theme/link tests pass; selection element retained | Main | Web + APK 29880625 verified |
| Usage-only updates rebuild transcript | 6d623197 separates transcript invalidation from usage/Info notifications |
Both-host regression failed before fix; Info still updates live | Main | Web + APK 29880625 verified |
| Open phone conversation becomes unread | 399d520c separates active reading identity from underlying list chrome |
Both-host regression failed before fix; other chats still become unread | Main | Web + APK 29880625 verified |
| Tabs are unmounted/revealed only after a detail finishes closing | 877c2f1a keeps the native destination mounted under its pushed route |
Real Navigator regression; detail covers tabs, Back immediately reveals laid-out destination | Main | Web + APK 29880625 verified |
| Server save closes editor before persistence succeeds | 25437b31 keeps draft/error/retry in editor, shows saving state, prevents duplicate sends |
Agent: 88 tests, four pre-fix failures; 12 browser checks/6 captures across both hosts | Merged main | Web + APK 29880625 verified |
Measured Back behavior
tool/chat_back_latency_probe.mjs serves the normal built app against the
loopback protocol fixture. Android user-agent selects Flutter's actual Android
theme/transition. Chrome CPU throttling is 4x, viewport 390x844. Metrics measure
from before pointer dispatch to the first frame reporting the returned chat-list
route. Route completion/ownership semantics are unchanged between builds.
| Controlled scenario | Before route settled | After route settled | Before/after maximum frame gap |
|---|---|---|---|
| 100 normal user/assistant pairs, quiet | 563 ms | 531 ms | 100 / 33 ms |
| 100 assistant messages folded into one turn, live text at 10 Hz | 1,153 ms | 563 ms | 400 / 117 ms |
| 199 assistant messages plus one user (one maximum history page), folded/live | 2,108 ms | 857 ms | 800 / 217 ms |
These are controlled browser samples, not device timings or statistical claims. The largest case reproduced the reported multi-second delay. Initial open/settle for that sample was about 4.05s for both builds; the change avoids repeating that rendering work while streaming/closing rather than deferring it to opening.
- Before: installed Docker web bundle, source from prior release.
- After:
build/ux_review_webfrom current source. - Captures and raw JSON:
build/ux-review-before-android-{heavy,large-turn,max-page}/and matchingbuild/ux-review-after-android-*directories. - No explicit multi-second wait/network await was found in Back. Flutter's normal Android toolbar/system-button fallback is 450ms, which cannot alone explain the reproduced delay. Native transitions/predictive gestures retained.
PageRoute.completedownership guard retained to prevent re-push during exit.- Optional
MAX_BACK_MS/MAX_FRAME_GAP_MSprobe budgets support repeatable lab regression checks without imposing flaky wall-clock assertions on unit tests.
Checks and limits
- 439 chat/shell/navigation tests passed, including predictive cancel/commit, disclosure identity, paging, focus, text, drafts, follow/read position and Info.
- Full gate: clean analysis and 1,848 tests pass, including added system text-scaling coverage for cached Markdown.
- Settings evidence:
settings-server-editor-save-ux.mdand isolatedtool/server_editor_save_probe.{dart,mjs}. Root remount during successful activation remains the root's existing behavior; no network wait added to Back. - Native Android performance remains unverified: no ADB, device install or capture. No transition-duration shortcuts, backend edits, workflow changes or production mutation tests. Changes remain confined to app/.
Delivery and regression evidence
- Source changes landed on main; settings commit ancestry checked after merge.
- Browser regressions pass: 12 navigation checks/9 captures in
build/ux-review-navigation-regression/; 17 chat/stage checks/10 captures inbuild/ux-review-chat-stage-regression/; 8 profile checks/5 captures inbuild/ux-review-settings-regression/. - Optional 4x-CPU maximum-page performance gate passed with budgets 1,500ms Back
and 400ms maximum frame gap. Under concurrent review load the sample settled
in 1,057ms with a 283ms maximum gap (
build/ux-review-back-performance-gate/). The paired comparison table above was measured separately without those concurrent Chrome regressions. ./install --websucceeded, with no shared-service restart. Existing public URLs retained by an atomic copy; rollback:app/build/web-before-ux-review-1792837775/.- Authenticated JS bytes match the installed bundle at localhost:8083 and public
HTTPS 8443/8096; unsigned bundle requests remain blocked. JS SHA256:
a3bb5a3394ff4baf405bf464b154820f9584e14353e2a408f95d80f782080437. ./install --apksucceeded: 29880625 (0.1.29880625), 65,398,506 bytes, assembleRelease 407.6 seconds. Cache key8d7dc9021ddfdd95f0b8matches current source/arguments; ZIP integrity/ARM64 payload checked. APK SHA256:99beda6311c37ab8e4acd3dd8ef7792ecab89ee3675517ca75ad3e939ddd2169.- Signature verification matches the existing debug signer;
aaptconfirms label Pipelines and unchanged package ID. Installed and public feeds published atomically, with full authenticated version/APK downloads verified at managed localhost:8083 and HTTPS 8443/8096. - APK rollback:
app/build/updates-before-ux-review-29880625/andapp/build/web/updates-before-ux-review-29880625/. - No phone installation or on-device verification performed.