Built to Work One-Handed, From the Menu to the Long Pages
Most actors update their website in the gaps: on a train, between appointments, in a car park before going in. So the admin is built to be usable one-handed on a phone rather than being a desktop tool that technically fits on a small screen.
Why phone scrolling is a different problem from desktop scrolling
This is worth understanding, because it explains a whole category of page that feels broken on a phone and fine on a laptop.
When you turn a mouse wheel over something that cannot scroll, the browser passes the gesture outward to whatever can. You never notice, because it just works. A finger does not get that courtesy. On touch, whatever sits under your fingertip claims the gesture, and if that thing cannot scroll, nothing happens at all. The page appears frozen.
The practical consequence is that any invisible layer sitting over the content will eat every swipe. So will any element that has quietly become a scroll container of its own. Neither shows up on a desktop, ever, which is why phone behavior has to be measured on a phone rather than reasoned about from a browser window made narrow.
What that means for how the admin is built
There is one scroll container per screen rather than several nested inside each other. Overlays that catch a tap to close a menu are derived directly from whether that menu is open, rather than from a separate flag kept in step by hand, because a second copy of a fact can drift from the first.
Heavy visual effects are applied by screen width. A frosted-glass blur on a card looks good and forces the browser to resample the background on every scrolled frame, which iOS Safari has never handled well inside a scrolling area. So it appears above 960 pixels and not below. The card is unchanged on a desktop and flat on a phone, which nobody notices and which is the difference between a page that scrolls and one that does not.
Content that fits
Card components clip anything wider than themselves, so content that overflows is not squeezed or made scrollable. It is simply not drawn. That makes narrow screens a correctness question rather than a comfort one, and it is why dashboard tiles and form rows are checked at phone width rather than assumed to reflow.
The general rule
Measure on the device. A counter on the page that reports where touches are actually landing answers in ten minutes what three plausible theories will not answer in a day.
Related: mobile menus, notification counters and real-time alerts. On the wider point, mobile optimization and user-friendly design.
Create a free actor website and build it from your phone if you want to.
