feat(web): cap + center content width on wide viewports - #108
Merged
Conversation
On the web the app runs full-width, so lists, cards, forms, and chat bubbles stretched edge-to-edge and were hard to scan on a desktop monitor. Add a shared `webContentMaxWidth` (820px reading column, centered) and apply it to the main scroll surfaces: the object list/detail/form renderers, the AI assistant (message column + input bar), and the tab screens (home/apps/search/more/ notifications/profile). It is a strict no-op on native and on narrow web — `maxWidth` simply never binds below 820px — so the phone layout is unchanged (verified: identical at 375px). The dashboard is intentionally left full-width; its responsive grid sizes widgets from the window width and benefits from the space. Per-row cap on the list keeps FlashList's virtualization intact (its contentContainerStyle is padding-only). Verified in the browser at desktop width: list cards, detail, and the AI chat sit in a centered ~820px column; at mobile width everything fills the viewport as before. 1281 tests pass, typecheck + lint clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The deferred web max-width item from the UX walkthrough.
On the web the app runs full-width, so lists, cards, forms, and chat bubbles stretched edge-to-edge and were hard to scan on a desktop monitor.
Change
A shared
webContentMaxWidth(820px centered reading column) applied to the main scroll surfaces:Safety
Strict no-op on native and narrow web — it's a
Platform.OS === "web"style andmaxWidthnever binds below 820px, so the phone layout is unchanged (verified identical at 375px). The dashboard is intentionally left full-width: its responsive grid sizes widgets from the window width and benefits from the space. The list cap is per-row, keeping FlashList's virtualization intact (itscontentContainerStyleis padding-only).Verification
1281 tests pass, typecheck + lint clean.
🤖 Generated with Claude Code