Linear — coding sessions on mobile
Keep code context visible on a phone while completing a comment-and-reply exchange. The keyboard entering and exiting marks the beginning and end of the input stage.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Linear — coding sessions on mobile · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Read code above and write comments below
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Linear — coding sessions on mobile · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="0" data-end="11"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Center the phone window, with code changes in the upper half and the input and keyboard below. When the keyboard enters, adjust the available height so that both the target code and current input remain visible.
Replace the keyboard with a processing state after submission
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Linear — coding sessions on mobile · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#090a0c}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="9" data-end="18"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>After the comment is submitted, the keyboard exits and the input area switches to an execution state; the reply appears after the processing state and continues to reference the same code context. Do not skip submission and waiting by swapping the entire image.
Keep narrow-screen information more concise than desktop content
Establish hierarchy with a dark phone interface, light sans-serif body text and cool purple accents; use monospace for code. Fit line lengths to the narrow screen and keep the keyboard sufficiently distinct from the input; place only a small amount of title text outside the phone, without crowding it with explanations.
Adapt to mobile reviews or task feedback
Keep the issue consistent when replacing code, comments and replies. This can be used for design reviews or publishing workflows, but always preserve the context → input → submit → process → reply dependencies; shorten waiting when reducing the duration, rather than removing states.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to another mobile review topic; preserve context references and reply dependencies.
Production constraints
Phone window / Code changes / Input field / On-screen keyboard / Processing state / Reply
- Keep code context above and the input and on-screen keyboard below; after submission, the keyboard exits and a processing state takes its place.
- Show the reply after the execution state; do not conceal timing by swapping the entire screenshot.