Mainstreaming RSS subscription user interfaces

We're having some interesting internal debates here at Yahoo! about RSS adoption.  There's at least some agreement that mainstreaming RSS subscriptions is about simplifying the signup user interface.  The research shows that "XML" doesn't have tangible value to people, even amongst those who know what it means.  If the orange XML button were on NASDAQ, you could make a quick buck shorting it, I'm sure.

We also know that verbs make much better calls to action than nouns.  So, what is the right verb for RSS feeds?  Is it "Subscribe"?  How about "Add"?  Or "Track"?

Tom Raftery thinks 'Subscribe' with a little tooltip next to it is the right way to present the experience.  Pete Freitag came up with a nice UI in his SoloSub experiment, but it's definitely missing a clear call-to-action for non-initiated users. 

Of course, Dave Winer, Jeremy Zawodny, Dare Obasanjo, Tim Bray and several others, have had debates about what the behavior of that button should be.  Regardless of the browser behavior, we still have a verb problem.

Yahoo! currently uses "Add Content" on My Yahoo!.  And that seems to have paid off pretty well, but it was designed for a dashboard interface.  In any other enviornment,  "Subscribe" is probably a better action word. 

However any research will tell you that people find the word "Subscribe" to be a loaded concept...it might have pay implications...it might mean that I have to do something to get something...it might mean I need to cancel something...it feels permanent.

Perhaps more importantly, the word "Subscribe" may be a conflicting term when you also have paid services that people subscribe to or email newsletters promoted on the same page.  

So, then you start thinking "Add Feeds" might make more sense, in general.  But where you are "Adding" these things becomes crucial to that experience.  And "Add" is being used in many different contexts for other content types.  It may work as the right action in a very specific context, but it can't be applied the moment you abstract the UI out of the local environment.  

If I'm on a news site somewhere, and I see a button to "Add Feeds" I have no idea where they are going and if I'll ever see them again after I "Add" them.  Does "Adding" a feed do the same thing as "Adding an Event" to my calendar?  Is it like "Adding" a friend in my social network?  Am I "Adding" two things together to make one thing?  There's no concept that I can have an ongoing relationship with the content of the feed with the word "Add".  And the word will get even less meaningful over time as there are more things people can add to more environments.

I would like to push for "Subscribe" and "Subscriptions", as it's a more scaleable nomenclature and more accurate for the experience.  But I have trouble arguing that mainstream users are ready to "Subscribe" to things as readily as they will "Add" things.  

If we're ever going to solve the chiclet overload problem, we need to come up with something that the 95% of the Internet audience who doesn't yet grasp RSS can relate to without having to be trained.

Of course, there’s a lot to do in terms of improving the ways people consume RSS, too.  But that’s a different debate.


Tags:  subscribe, xml, rss, yahoo

Comments:

Re: Mainstreaming RSS subscription user interfaces
by stephrieger on Tue 06 Dec 2005 08:37 AM EST

I'm not a big fan of jargon. And from a real worls (non-geek) user, jargon is terribly intimidating-especially when dealing with a call to action-style scenario. While the Yahoo approach works, it may be that they also benefit from added context. Adding a contact, in the context of MyYahoo carries the benefit of trust that Yahoo may have created with the user. If you trust Yahoo tools, you probably trust that whatever you're 'adding,' you will also be able to remove.

But in an anonymous brower scenario, the trust may not be there-especially for novice users who often see the browser as equivalent to the internet (i.e. do not differentiate applications from the content they contain.) So it's a difficult question. I do agree that 'subscribe' is a loaded word for many consumers and that 'add' is not much better as again, you lack context ("add to what?")

What may help resolve the issue is better integration between browsers and feedreaders so that the user gets immediate visual feedback of the addition as well as the ability to manage/remove the addition.

Trackbacks:

TrackBack URL:
http://www.mattmcalister.com/blog/_trackback/1413276

Mainstreaming RSS subscription user interfaces
Weblog:  Nooked Blog
Excerpt:  Matt McAlister raises some great points on "RSS Subscribing" I agree - we need to fix the "visual" problem at least "Subscribe" vs "Add" - its a tough one as Matt points out.. I think most people buy into the...
Posted:  Mon Nov 21 10:39:48 EST 2005
Mainstreaming RSS subscription user interfaces