I got feedback this week that we should have written the GitHub issues differently. I was told we should have explained more why they are an issue, so that the developers are more motivated to solve them.
I experience the disorienting loss of vertical scroll position in many of the apps and websites I use. Twitter and other stream interfaces update the feed while you’re scrolling, losing your place. Page and card interactions often plop you back at the top of a list when you hit the back button, especially if there are filters active.
I’ll illustrate with wordpress.com since I use it a lot and helped make it.
In the screenshot below, I scrolled the theme browser down a bit.
And then clicked the “Shoreditch” theme.
And then clicked “<- All Themes” to go back.
And lost my scroll position.
A gallery style browser that loses vertical scroll position is very frustrating. Repeated grid and list scanning is headache inducing and exhausting.
I spend too much time getting back to where I was, trying not to fall out of high memory state, trying not to crash my stack. Vertical scroll position is sacred. The back button should take me back to where I was, not respawn me at the checkpoint at the beginning of the dungeon. It should not be a quest restart button.
Here’s another example on wordpress.com. In the following shot, I scrolled some search results down a bit.
And then clicked on a post in the list to open the editor and peek at the contents.
And clicked “Close” to go back to the blog posts list.
And lost my vertical scroll position. During searches, I often dip in and out of the editor looking for what I want. Repeatedly losing scroll position makes this so frustrating and slow.
One more example, this time with Netflix.
Click a show to start playing.
Click the back button to go back to the video grid.
Lose your place.
I felt frissons of frustration and loss back in the 1980s when my fingers —my little stack pointers and quest markers—slipped from the leaves of my choose your own adventure books. Now, I experience those feelings with regularity in my relationships with software. I regret associating those physical memories with a common software interaction bug: one that, seemingly, many of us can’t reliably fix.
The occasional slipped finger added to the sense of journey and questing. Repeated, daily loss of scroll position merits no associations with nostalgic sepia. The complex software interfaces I use today fail as custodians of context more reliably than did my 10 year old fingers.
I recall removing the Links Manager from WordPress back in 2012 amidst snickers about how old school and old fashioned blogrolls were in the age of social media.
I like the idea of graduating the old sidebar blogroll to a Following page. I started experimenting in that direction. I’m playing with feedbase.io, currently. Here’s my feedbase blogroll—heavy on education, neurodiversity, the social model of disability, and tech ethics.
I’m watching the space with interest. I see both educators and tech workers talking about the possibilities of subscribing to dynamic blogrolls.
So the first step is to fill the database with feeds, and give people a way to subscribe and unsubscribe. To accept OPML files as input too. And to publish a list of subscriptions that is dynamic, that other apps will in turn subscribe to. I’m working with the developers of two new RSS reader apps that will hook into this feed database.
- A Following Page (aka some significant updates to my Blogroll)
- RSS Readers Are Due for a Comeback: Feedly, The Old Reader, Inoreader | WIRED
- Feed reader developers — here’s an easy way to differentiate your service and have your users love you even more
- 📓 A Custom OPML Request of Blogs associated with Primary Education and Leadership – Read Write Collect
- Scripting News: A database of feeds
- Scripting News: Here comes feedBase!
- Scripting News: First feedBase demo