What happened to feed auto-discovery in Firefox 4?
TL;DR: The feed button is not dead; it's just been sent to sing backup in Firefox 4 because it's not pulling its weight. This post talks about why things have changed.
There's a brouhaha about Bug 578967, wherein the feed auto-discover icon in the Firefox 4 Beta has been hidden by default. Being a feed nerd, the author of a book on the stuff, and a Mozilla employee—I've got at least a few opinions.
This post is one of several on this subject.
Defaults are hard to pare down
The feed icon still lives in the Firefox 4 Beta; it's just not there by default any more. But, if you look at the controls available in the toolbar customization panel, you'll notice a lot of things that don't show up by default—there are a lot of things in there, period.
This is the dilemma for the Firefox User Experience team at Mozilla: Like it or not, one of the main themes of this next generation of browsers is minimalism—faster, smaller, less browser to get in the way of what you're browsing. Yet, at the same time, Firefox 4 has the features of Firefox 3.6 and more.
You can't just cram it all in there, so what gets prime real estate by default? People say it's just a few pixels, that feed button—but is it so much more important than anything else that could go there? And before you answer, consider that not just for your personal use, but for the 100's of millions of people using Firefox. How do you check your own biases and make a decision on that scale? You could make an educated guess, make a gut check. A lot of brilliant design happens that way.
You can also gather some telemetry from beta installs to see what people really use. Looking at a heatmap of clicks, the feed button is an absolute stinker. This isn't a random whim of the UX team—seriously, it's an order of magnitude less used than anything else in the toolbar (notice the one black spot):
There have been comments dismissing the validity of that heatmap study. But, as far as I can tell, none of them really stick. So, for the sake of argument and a shorter blog post, let's assume barely anyone is using the feed icon and that it's not pulling its weight in this new age of browser minimalism.
Keep in mind that Firefox isn't the only browser to deprioritize the feed button: Google Chrome doesn't even have a feed button at all, and for many people that's the gold standard for minimal browser UI:
Serving the users
Let's hammer on the point of disuse some more—what's the payoff for clicking that thing, anyway?
+1 — You get an option to create a Live Bookmark, which is really handy for things like Bugzilla searches or light headline reading. (I like those so much that I tried building them on the server at Delicious once, but we never quite worked it out at scale.)
0 — You get a list of sites to which Firefox will delegate subscription, if you happen to have installed a content handler. Useful if you know what it's about; a mystery if you don't—not much more useful than a bookmarklet, to me.
-1 — You get a plainly-styled version of what you were probably already looking at on a site, something I criticized back in 2006, like some are criticizing the feed icon change now. (At the time, I was working for a marketing company, and the change cost me days trying to incorporate branding in feeds on a client's site. I think we gave up after a bit, but I suspect that FeedBurner built a nice business routing around that change.)
That's been status quo for years, and it's less than compelling—I've even had people ask me if they broke the page when the button was clicked on accident.
So, given little reward for clicking that feed icon, pushing it into the background in its current state is a service to the users of Firefox. In other words, that feed button has to get a lot more interesting if it's going to serve alongside UI all-stars like Back, Reload, and Location.
Hell, even with Firebug installed, I use View Source more than the feed button these days, and I've never stuck that on the toolbar.
Leading the web
The most compelling response I've seen to the "removal" of the feed auto-discovery button is the challenge that Mozilla and other browser makers should be improving feed-related features, rather than pushing them into the background. With this, I wholeheartedly agree—but I'm not entirely sure what to do about it.
So, there's a balance here: Make the experience of the web better by improving how Firefox handles what's already out there, and make the web itself better by building more powerful and enabling technologies into Firefox and other products. In the best of times, Mozilla can do and has done both at once. WebGL and technologies associated with HTML5 represent great examples of this.
But, alas, syndication feeds in the browser have stagnated. The feed button has been a weak feature for years. In the meantime, other things have taken priority in the Firefox project. The rise of Twitter and Facebook and more complex applications on the web have reduced the need for most people to interact directly with feeds, so demands for attention to the feed button haven't exactly topped the charts in comparison to things like making sure Flash doesn't crash the browser and getting super fast for everything else.
In the end, Mozilla has a browser to ship. The decision on the feed button has been made and, believe it or not, with a great deal of thought behind it.
I know that this is the first time many people have heard of this change, but many already have heard and have given the UX team a number of earsful. Coming in at this late stage and requesting—nay demanding—a reversal of that decision will do nothing but piss off all the people who've been banging away at this and many other things up to now. They're people who've worked hard, stayed up late—and the last thing anyone wants to do is rehash every conversation ever about the topic.
I understand that we always try to enhance UI of any software and that it takes a lot of time and discussions to make decisions. And some decisions may not please everyone.
As for the Feed button, the one in the toolbar customization panel does not highlight when there are feeds available or change colour when there are no feeds. You need to click on it to see if Firefox 4 discovered feeds of not.
In Firefox 3.6, you don't need to guess or click on a button to find if a feed is available.
So instead of a feed button that is always shown, feed available or not, it's much more usable to show a button that highlight properly (takes more space), or is shown only when feeds are available (optimal space use).
Using a heatmap of clicks does not do justice to the feeds button, since it's of no use to click on it in Firefox 3.6 to instantly see if or not there is a feeds available.
There are other information that have been removed in Firefox 4 that are open to discussion.
For example, a heatmap does not show loading icons, throbbers, urls loading in the status bar, "done" message in the status bar, etc. In fact, any status information won't show up in a clicks heatmap. So if that information does not show up in a clicks heatmap, it does not mean these statuses must be removed from the UI.
Actually, the Feed button in the toolbar does change state depending on the presence or absence of feeds: It's enabled and clickable with a feed, and greys out without a feed. I mentioned that in the post. If that's not noticeable enough for you, then that's a separate bug specific to that button.
As for the validity of the heatmap—what would you suggest get done as an alternative? There's no way to fit a large number of beta users with eye-tracking gear. Also, I personally don't buy that people just like to have the feed indicator around because it's nice to see it light up. It's a call to action (eg. subscribe to this site)—and if barely anyone takes that action, how valuable can it be?
And if you really miss the feed-autodiscovery feature, just use RSS Icon In Awesombar. ;)
RSS/Atom are standardized web features, it's a shame we have to rely on 3rd parties to enable support. At least Google has an official RSS extension so I can trust the security of the addon, but still, both Mozilla and Google are going backwards on this.
Well argued. I am a little disappointed with its removal because RSS is a distributed status update mechanism, and we're currently being swamped by centralised status update mechanisms (twitter and whatnot). But the experience has always been seriously crap (to put it bluntly), so better to remove it until it improves I suppose.
Sadly, my guess is that once its removed, it will never reappear.
i agree with the new UI concerning feed subscription (along with bookmarks).
But there is indeed a concern with Firefox 4 concerning feeds. Since Firefox doesn't really handle feeds, Sync doesn't care about them either. Therefore if you have installed an add-on to deal with feeds, they will not be synchronized and that's not a good experience for the user. Bookmarks are synchronized but feeds are not, whereas they supposed to belong to the same scheme
Good points. I'd say there are lots of things Firefox could do better with feeds in general.
I think this is right decision even I'm one of the people who use RSS button which is inside location bar. But we have extensions right? Because this function is important for me I created extension RSS Icon In Awesombar which brings this button back to the location bar.
The only reason i'll even get to see your follow-up entries to this is because my browser includes an rss reader and a button that tells me you have an rss feed for your blog.
So, you mean to tell me that you didn't already think my blog had a feed, before you looked for the feed icon?
Are you surprised he would be more likely to find an RSS button on his toolbar than somewhere on the side of the page? Or that someone wouldn't assume that all blogs have RSS, especially many older ones? Or that asking Google Reader to test if a URL had a feed is a whole lot more cumbersome than using the browser to get Google Reader to subscribe to it?
I stumble upon too many blogs of various kinds that have no feeds to make the assumption that every blog has one. As i mentioned on your other post, Yahoo Pipes is a tool i often need to resort to.
Maybe you need to step outside your Web 2.0 bubble sometime?
I suggest removing the Scroll Left button, it's used only by 1% of Fx users.
I'm pretty sure removing the Scroll Left button was discussed—if only for a minute—and a call was made that basic spatial navigation was more important than feeds.
Janusz, I totally agree, let's remove the site identity, remove bookmark, more info, scroll right, print menu item, save page as, bookmarks all tab, etc., they are obviously never used.
Pretty much all of those you list are used more than twice as much as the feed icon, or don't appear on the toolbar at all.
I can put "View Source" in the toolbar? How?!
Actually, for "View Source", I installed the Web Developer add-on. So, that's not built-in like I implied.
Why do you care about this "Back" button, "Location bar" and so on ? Just put one big "facebook" button and one big "google" button, it's enough...
With this kind of decisions, I think you are not "building a better Internet" as Mozilla Foundation is supposed to do.
RSS and twitter are very different ways to access information, with their "+" and "-". Leaving RSS dying seems to me a regression. I am sorry, but when I read "The rise of Twitter and Facebook and more complex applications on the web have reduced the need for most people to interact directly with feeds", I am a bit frightened, because I understand it a bit like : "Hey guy, why don't you go on Facebook like everybody to surf the web. It's cool and your friends tell you what is interesting to read".
I don'k know about the usability of the feed concept, it could be certainly improved, but I really felt it was going towards "give people tools to take control of their online lives" (Mozilla Mission)
So, I did say that Twitter and Facebook has left users with less need to interact with feeds—but I didn't say that I liked it. I'm the last person who'd want closed silos to own the web, and I want to see RSS and Atom and other open web technologies grow.
I'm currently a Chrome user, wishing that 1 day Firefox will go back to why I liked it in the first place. I've been subsribing to Twitter feeds and Facebook pages more than I have with feeds with Chrome, not only because the prior are established, but also because Chrome doesn't encourage RSS with its exclusion. I don't bother with addons either, I don't think most users do either (yet Mozilla decides addons need a whole bar).
I can't be the only person who, when I decide I want to subscribe to a site, looks for the RSS Icon on the page first before I ever even glance at the auto-discovery icon. In many cases, especially on larger sites, I rarely want what they would consider the "main" feed anyway and on the sites where I do want that, their feed is usually in a place that's easily clicked on.
So, in my case, it was needless clutter that I'm rather happy to see getting removed by default. Of course, I remove a lot more than that from Firefox's chrome, but at least this is one less thing I have to do manually.
Sir, looks like you know a lot about FF. Is it a conscious decision to not have Awesombar as the default search bar .i hate it when it gives me google search results. if i type bbc news and hit enter, it should take me to bbc news site, right? not a google search of it? If there is any way i can get my awesombar back, please let me know.
Sincerely, fflover :)
Sounds like you might be interested in this add-on:
beta users is not equal to representative user population. how much percent of all Firefox users does your study cover, is it enough to make statistical conclusions?
Well, it's not my study, it's the Test Pilot team's study. I'd say it's a decent chunk of users, with some interesting segmentation. But, that's my opinion. If you have an idea of how to execute a study that covers more, feel free to let the Test Pilot team know.
Wow. There's a lot of strong feelings flying around. Well as one of the silent majority I'd just like to offer my support to the removal. I never used the feed button and whenever I wanted a sites feed I normally scanned the page I was on for an icon to click.
Thank you for your post. I, too, would rather have the button clutter up a little than risk RSS being less discovered. But I understand your point and respect your decisions.
your metric for evaluating the utility of the feed button -- click rate -- is about as incorrect and contrary as possibly can be conceived.
the entire point of the feed button is that you only need to click it once for a site. after a user clicks it, the user shouldn't have to click it again on that site, and, going further, shouldn't even have to visit the site. those are the signals for success.
if you want a useful metric, dont look at how often the button is clicked. that's entirely the purpose of what it's trying to avoid. look at return rates for sites where a user has clicked the feed button. if you see a precipitous drop in return rates, you know the button is functioning completely as desired. the bigger the drop, the less users return, the better the button works.
baby HCI jesus is weeping in his crib.
So... if it only gets used once per site, then it doesn't belong in the same toolbar with navigational controls that get used constantly. It's a special action, used rarely. Thus, it's in the bookmark menu now - you know, bookmarks, another thing you ideally do once per site if at all.
But as I've said in other comments, if you feel strongly enough, come up with a study to propose to the Test Pilot team and spread your HCI jesus gospel