Repository navigation
Conversation
Titled screens already shared a 96 disc and title, but the first row landed at a different height on every screen and platform: Android left 24 under the title, iOS 36, the web whatever each page added, and the empty scene was centred in 0.42, 0.34 or 0.32 of the screen depending on the call site. LayoutTokens (shared) holds one set of ratios: content starts at 0.38 of the screen height, the gap under the title is held between 36 and 64, and every empty scene sits in a 0.36 slot. Each client measures where its own title ends and spends what reaches the line, so Android and iOS start on the same y. iOS keeps its position on the 874pt phone it was drawn for. Android reads the Kotlin object; iOS and web read generated copies gated by verifyLayoutTokens in both CI workflows. Root feeds are unchanged.
Align screen content start and empty scenes by screen-height ratio
ohmzi
enabled auto-merge
November 9, 2026 18:09
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
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.
What ships
:shared:verifyLayoutTokensdrift gate inpr-gate.ymlandrelease.yml.No database migration, no API change, no new Guide topic (spacing only).
Verification
CI on #51 was green (9 checks). Locally: shared tests and the four codegen drift gates, Android compile plus 906 unit tests, web lint / 2094 tests / build. No device pass on any platform yet; iOS was only compiled by macOS CI.
Merging publishes the release; the live instance is updated separately with
scripts/deploy-release.sh.