Re:Communicating with Interactive Articles
by Veuxdo on Sunday February 12, 2023 @12:36PM
(#34764826)
Very interesting. I'm working on on app that has "slides" users click a button to progress through. Now I'm wondering if users would prefer to "scroll" through the content instead.
Re:Communicating with Interactive Articles
by sethherr on Sunday February 12, 2023 @05:02PM
(#34767561)
I can say there has never been a time where I’ve preferred having a button instead of scrolling.
I’ve interacted with sites where scrolling locked in to pages, and I thought that was fine (As I say this, that sounds like “swiping” - which I think is fine and feels intuitive).
Re:Communicating with Interactive Articles
by Kinrany on Sunday February 12, 2023 @01:35PM
(#34765429)
Note that this is the same as us programmers preferring to have a single interface for many things instead of several mutually incompatible ones.
Also similar to how iterators are a fantastic API in most cases: lots of things can be built on top of getting the next item.
> The New York Times provided one of the few available data points, stating that only a fraction of readers interact with non-static content, and suggested that designers should move away from interactivity
Then their citation [1] mentions: "Why? ... Users just want to scroll"
It seems like this is the approach a lot of interactive articles use these days, where most of the "interactive" content is still shown by default as the user scrolls.
[1] https://github.com/archietse/malofiej-2016/blob/master/tse-m...