You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Horizontal apps place navigation at the bottom (thumb reach on mobile) or the left (desktop), keyed to the primary reading axis. In a vertical, RTL interface the primary axis is down-the-column and columns flow right-to-left — so the "natural" home for a rail is genuinely unclear.
Where it shows up here:tabs, chapter-navigation, and the chrome of Vertically Verse.
Open questions:
Does the rail belong on the right (the reading origin) or the left (the reading destination)?
Bottom-bar thumb ergonomics vs. reading-axis consistency — which do users forgive?
Should the rail itself be set vertically, and if so, top-to-bottom or bottom-to-top?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Labels:
RFCnavigationHorizontal apps place navigation at the bottom (thumb reach on mobile) or the left (desktop), keyed to the primary reading axis. In a vertical, RTL interface the primary axis is down-the-column and columns flow right-to-left — so the "natural" home for a rail is genuinely unclear.
Where it shows up here:
tabs,chapter-navigation, and the chrome of Vertically Verse.Open questions:
Write-up: https://vertically.works/challenges#navigation-direction
Propose your answer as a PR. Strong answers get merged into the spec.
All reactions