A dark theme is not the light one inverted, and a narrow screen is not a desktop with things removed. Doing either badly is worse than not doing it, because a wrong number in a low contrast cell and a quotation composed on a phone are both ways this platform loses money for somebody.
So both answers here are partly a list of what the system declines. Dark is a selected palette with its own measured values. And there is no phone view. Tripbooks is a desktop and tablet product, three supported widths, and below 768 pixels it says so rather than degrading into something that half works.
Drawn fresh from the Untitled kit and the system’s ruled tokens, not restyled from the originals.
You were sent BKG-7QP2K4M9. We can put it back in your inbox for when you are at a desk.
Send it to my inboxBelow 768, every route renders this one designed screen: a hand-off, not a dead end.
Every value below was checked rather than chosen by eye. The five disposition texts clear 6.3 to 9.6 against the card, well above the readable floor, and the sequential ramp is monotonic in the opposite direction to the light one.
Chrome gives up space first. The rail collapses to icons at 1024 and to a drawer at 768. The table keeps every column it had and scrolls sideways inside its own frame, which is the honest answer for a register whose columns were all chosen for a reason.
A table that scrolls sideways has one failure mode, and it is a serious one on this platform: you scroll to the outstanding balance, look up, and no longer know whose balance it is. So the identity column is sticky and everything else moves under it. That single decision is what makes horizontal scrolling safe for money.
There is no phone view and there is not going to be one. Tripbooks is an operating system for a travel business: ten column registers, six figure documents, a margin floor, a credit gate. None of that becomes safer by being reachable from a pocket, and a composer that technically renders on a phone gets used twice and produces two quotations somebody has to apologise for.
So the boundary is drawn once, at 768, for the whole platform, and it is a designed screen rather than a broken one.
I had drafted a phone layout in which the register became a list of two line cards, which meant writing a boundary into the one line per cell law. With no phone view and no dropped columns, the law holds absolutely. A register is the same table at 768, at 1024 and at 1280. Thirty-one pixel rows, one line per cell, ten columns, no wrap. The narrower the screen, the more of it you reach by scrolling.
I had written a three tier priority system where each field declared whether it survived to 768, 1024 or 1280. It was tidy and it was wrong, because every column on a Tripbooks register was put there by somebody who needed it, and a system that decides on their behalf which of their columns matter is making an editorial judgement it has no standing to make. Scrolling makes that judgement unnecessary.
Somebody who opens a link on a phone was sent that link for a reason, usually by a colleague, usually about one record. The screen shows the reference they were sent and offers to put it back in their inbox for when they are at a desk. That is the entire job, and it is the difference between a dead end and a hand-off.
Every register, every record, the composer, the marketplace, the settings page and six customer facing documents, each of which would otherwise need a phone layout, a phone test and a phone bug list. The one place a narrow screen still matters is the customer facing share pages, which stay fully responsive to 375, because a traveller reading an itinerary on a train is the primary case there and always was.