3 ms·
Bummer. I played with Spritz (a centered-text speed reading API) at a hackathon a while back, and was pretty impressed. It seemed that I could read with real
by clay_to_n 11y ago
Bummer. I played with Spritz (a centered-text speed reading API) at a hackathon a while back, and was pretty impressed. It seemed that I could read with real comprehension at around 400WPH and "skim" at about 1000. A big part of your pitch was "moving from word to word takes most of the time while reading," and I thought they had research to support that.
It's still a fun thing to try if you haven't done it yet. The article points out what is pretty clearly the biggest problem with these speed readers - going back to re-read is a big UX challenge. My little hackathon app used a "back ten words" button (may have been what Spritz recommended?), but I also thought having the actual paragraphs scrolling above the Spritz text as you read would be a more useful way of solving this problem. If you get lost, skim the paragraphs around what you're reading, and press / click a word you want to start speedreading from again. In more dense material where you need to flip back a page or two, you might need some sort of zoom out functionality as well.
If nothing else, these technologies will hopefully find a use in wearables and other tiny-screen devices.
- EGreg 11y agoYes, tech assisted speed reading should actually work while retaining comprehension, as your eyes don't move.
- rsfern 11y agoThe review article here suggests that language processing steps are the bottleneck, not we movement. So the reasearch suggests that current approach to using tech (rapid serial display of words) introduces a speed-comprehension trade off. Perhaps a better approach would be to develop deep learning systems that sort of translate cumbersome writing into linguistic structures that our brains can more easily/quickly digest?
- adrianN 11y agoThose systems already exist, they're usually called editors. Sadly, they seem to be used less and less.