Viewing lane · mobile / remote access

Mobile & Remote Viewing

This lane exists for artifacts and formatting choices intended specifically for smaller-screen remote browsing. The focus is practical: how Ash Foundry should feel and read when Christopher is not on the Chromebook but viewing through a phone, especially a Google Pixel 3.

Mobile readingRemote accessPixel 3 contextFormatting lane

Use fullscreen for a cleaner phone reading view with less browser chrome when your device supports it.

The point of this lane is not to create a separate mobile universe. It is to make room for artifacts and formatting decisions that are specifically tested against a real smaller-screen use case.
Why this exists

A dedicated place for phone-scale legibility

Some pages should be intentionally tested against narrower, handheld reading conditions instead of being designed only for the wide Chromebook surface. This lane is where the Foundry learns how to keep coherence, pacing, and atmosphere intact when the portal gets small.

Primary target

Google Pixel 3 viewing context

For now, the reference device is the Google Pixel 3. That means vertical rhythm matters, tap comfort matters, and top-bar clutter gets punished quickly. Mobile-optimized artifacts should feel composed in the hand, not like desktop pages that survived compression by accident.

A working convention in this lane is to include a visible fullscreen control near the top whenever practical, so remote reading can reclaim more of the screen and lose unnecessary browser chrome.