feat(studio): mobile and PWA interaction round - #985
Closed
jtenniswood wants to merge 1 commit into
Closed
Conversation
The cross-cutting mobile smear from the original branch, landed once at its net state (the reverted bottom-nav intermediate never existed here): responsive branches across the chat surface — sheet-based side panels, the docked composer with keyboard handling (it never steals focus on mobile), safe areas, long-press row actions, swipe dismiss, mobile thread scroll, and the bottom tab bar interplay. The UI kit is untouched (sheet.tsx has been at its final state since the foundation PR); PWA manifest/icons landed with the chrome, so this PR is behavior only. Every hunk sits behind useMobile or a breakpoint — desktop rendering is unchanged, which is the reviewable claim; Playwright runs desktop Chromium, so all specs are structurally untouched. The six staged chat files reach their final, original-branch-identical state. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jtenniswood
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack 20/21 — Studio: mobile and PWA interaction round
The cross-cutting mobile smear (~45 churn commits on the original branch) landed once at net state — the reverted bottom-nav intermediate never existed here.
useMobile/breakpoint branches across the six chat files: sheet-based side panels, the docked composer with iOS/Android keyboard handling (the composer never steals focus on mobile), safe areas, long-press row actions, swipe dismiss, mobile thread scroll, the bottom tab bar interplay.sheet.tsxhas been at its final state since PR 1, so this PR is behavior, not kit churn. PWA manifest/icons landed with PR 1's chrome.use-agent-chat,chat-view,chat-workspace,chat-input,message-bubble,session-sidebar) reach their final, original-branch-identical state here.useMobileor a breakpoint — desktop rendering is byte-identical, which is the reviewable claim; Playwright runs desktop Chromium, so all specs are structurally untouched.Demo at this stack point: open Studio on a phone via the LAN dev origin, install it as a PWA, drive a chat with the docked composer and bottom tabs.
Part of the stacked landing of #618.
🤖 Generated with Claude Code