A new interaction paradigm for AI chat. The bot doesn't type back. It flashes.
<aside> 💡
What if reading an AI response felt less like scanning a wall of text and more like watching words arrive — one at a time, right where your eyes already are?
</aside>
A conversational interface where the bot’s responses are delivered via Rapid Serial Visual Presentation (RSVP). Words flash sequentially at a fixed focal point, at a pace tuned to the reader. No scrolling. No scanning. Just reading, effortlessly.
The hypothesis: RSVP isn't just faster. It's a fundamentally better match for how the brain processes language in a chat context.
RSVP has a long history in reading science. The basic mechanic dates to the 1970s, when researchers discovered that much of the time spent "reading" is actually spent moving your eyes. A third of reading time spent on eye scanning and regressions without adding comprehension.
Fix the text. Move the words. Let the eye stay still.
Studies through the 80s and 90s showed trained readers could process RSVP streams at 500–700 words per minute with strong retention. This well above the average reading speed of ~250 wpm for on-screen text. More recent work (Benedetto et al., 2015; Masson, 1983) confirmed comprehension holds at moderate speeds before degrading sharply above ~600 wpm, suggesting a practical sweet spot.
The challenge: RSVP strips context. Traditional readers dont allow the user to glance back, and you can't skim ahead. For reference material or complex prose, that's a real cost. So I was curious how to solve for that.
The experience stripped everything back to one focal point — center screen, slightly above midline. Words arrived one at a time at a default pace of 280 wpm, adjustable in real time via a scroll gesture. A subtle blur transition signaled phrase boundaries instead of punctuation pauses.
Users could tap to pause, double-tap to replay. A ghost trail of both past and future content lingers at a reduced opacity so that there is a small concession to the brain's need for backward reference without breaking the flow.
The input side stayed familiar. You type normally. The bot responds in RSVP. Asymmetry by design. If the user wishes to see the traditional chat history theres a page they can drill down into for referencing the conversation in the traditional format.