No study compares the same content as an interactive article and as a static one. When interaction was added to the same chart, none of the variants in one set of experiments beat the static version. What helped was readers doing something with the figure, and the gap disappeared once the comparison group also did something. Readers use the component that responds at a touch and sits in the middle of the narrative; about half of desktop readers never opened content placed behind a click. One long-time maker of interactive tutorials says each takes one to five months, including the time to learn the algorithm.
Adding a graphic raises reading comprehension by about 0.39 standard deviations on average. Placing each diagram next to the text that explains it, and having readers do something with a diagram rather than just look at it, each have research behind them and cost less than drawing one more diagram, though no experiment compares them directly with adding a diagram; only one experiment isolated prediction, and it found no detectable difference. Use a state table for step-by-step execution, a numbered list for a single-path flow, and a table for comparisons. On a phone, a mermaid diagram with more than 3 nodes side by side in one rank shrinks until the text is unreadable.
Put a video at the top if it covers the whole article, at the start of a section if it covers only that section; videos at the bottom often get skipped. Readers mostly rewatch specific segments, so every section should link to its timestamp and the intro should state the video's length. Prequestions and writing your own explanation after each segment have experimental support, but those experiments all used short material, a little over 20 minutes at most.
Research interfaces share one move: keep the video and the matching text visible together, either beside the text or right at the passage being read. In the 16-person Papeos study, the condition with clips attached to passages had the lowest mean mental demand (the omnibus test across three conditions was significant). No experiment has compared layouts for a long written guide paired with a lecture recording, and no research I found says what to do on phones.
Looplane's TUI and plain CLI are two interfaces over the same runtime paths. The CLI selects a presentation mode from TTY state and flags, runners emit events, and the TUI projects those events into thinking, tool, approval, verification, and terminal states. The screen distinguishes native and external runtimes without treating UI entry points as proof of backend maturity.
When processing requests, Claude Code randomly displays one of 185 built-in verbs (like Thinking, Brewing, Clauding), then picks one of 8 completion verbs with elapsed time. You can customize these via spinnerVerbs in settings.json, using either replace or append mode. All data in this post is verified directly from cli.js source code.
LLM generation takes 3-5 seconds, and waiting for the full response before displaying it makes for a terrible experience. SSE pushes tokens as they're generated, reducing time-to-first-character from 5 seconds to under 1 second.
DaoDao is not a content platform -- it's a learning connector. Using anti-perfectionism design, community co-learning, and zero-decision recommendations, it helps learners bridge the execution gap -- from vague ideas to actionable plans.