> The UI as it stands is technically functional and easy to understand, but not exactly effortless or convenient to use. In particular, there's quite a jarring

> The UI as it stands is technically functional and easy to understand, but not exactly effortless or convenient to use. In particular, there's quite a jarring difference between the modes during switch, making comparison impossible. Agreed about the jarringness. I actually had a section about how jarring it felt (I'm the author of the blog post) but scrapped it because I was spending too much time on the post :D > An inline UI next to/within the content, with some logic to ensure the nearest content to the control stays at the same scroll-position during change would help a lot with this. Cool ideas. I initially wrote off the UI idea as low ROI (as you can see in the post) but maybe my opinion would change if I saw someone really nail this feature. Also, the low ROI comment only applies if we have to manually markup the content. If we can automate that side of it, then that changes the ROI equation.