Here are three little tweaks that go a long way in improving one’s browsing experience and should become default features on every website.
Kottke’s unread posts notification in the title bar
It’s not just web applications like Gmail or Twitter that can enforce the “push” instead of “pull” format that is associated with the real-time web. If you spend a significant amount of time browsing Jason Kottke’s site you’ll probably notice the title bar changing when a new post gets published.
I added a new feature to kottke.org over the weekend: live updating on the home page. If you leave kottke.org open in your browser (with JavaScript on) and I post a new link, the page will display a message urging you to refresh to view some new posts. The page title changes too, so if you have it up in a tab, you can tell at a glance if something’s new. Right now the page checks for new posts every ten minutes, but that could change depending on server load, etc. Thanks to Twitter Search and Tumblr for the inspiration.
Developer hack: Kottke didn’t give details on how he did it, but this script is doing the work.
Infinite scrolling
Paginated websites make digesting content more manageable, but sometimes you just want to consume as much as possible too. Imagine devouring as many Google search results and Flickr images as you can.
Infinite scrolling—at least the hacks mentioned below—load the next page when you’re done browsing the current one. The next and previous page links are still there, so you have both options to choose from.
User hack: install Greasemonkey and the AutoPagerize user script.
Developer hack: use the jQuery plugin or the WordPress plugin.
FFFFOUND!’s keyboard navigation
Don’t underestimate the efficiency of the keyboard. At image-bookmarking site FFFFOUND!, using the keyboard is the best way to get around.
Developer hack: install paging_keys_js.
Here’s another technology being given the Real Time Web treatment: RSS. There’s PubSubHubbub (PuSH), created by the mother of all search engines and there’s rssCloud, created by the father of RSS. You can tell just by the people behind both projects that this is a Big Deal.
I won’t get into the technical details—mostly because I can’t—but these two protocols are built on the same idea of push notifications instead of pull, which is the current setup. Feed aggregators won’t have to check every now and then for any updates; they’ll come right in when they’re published.
The score seems to be in PubSubHubbub’s favor right now, and it certainly calls attenion based on name alone. But Dave Winer had the idea as early as 2001. And who knows what will happen in the next few months.
What matters is the feed reading system is getting a much needed upgrade especially with all this talk of it being dead. RSS? Dead?
Like Bwana, I scoff at people who run through the streets proclaiming “RSS is dead! Long live Twitter!” Aside from the obvious non-parallel comparison between a protocol and a web app, he explains it nicely:
Those who claim RSS is dead don’t realize their newfound love for Twitter would be moot if it were not for RSS. Breaking news on Twitter comes from two main sources in my mind: websites and personal experience. For tech news, I doubt there is much personal experience for news unless there’s a conference or an event. Most juicy, 0-day news comes from websites. These websites often have a… wait for it… RSS feed. The race to post tech news first on Twitter usually stems from who can refresh their RSS reader the fastest.
So here’s to RSS: I’m not sure what the Web would do without you. Pretty sure that’s how many feel about Twitter too, but let’s talk again when it goes from webapp/API level down to the protocol level. And when it scales properly, of course.
Postscript: Both PuSH and rssCloud support Atom. RSS and Atom are both feed delivery mechanisms, but you won’t see people yelling “feeds are dead!” or “Atom is dead!”, as they have ignored any distinctions among the three for ages now. So for the sake of simplicity I mentioned only RSS above.
Just about the time it’s become almost trivial to create rounded corners, Facebook suddenly decides to go back to its originally boxy, “razor cut” look. In the announcement, the Facebook design team reveals its priority:
Since we introduced rounded corners to Facebook, their consistent use has been spotty at best. The corner radii vary, and it sometimes feels arbitrary which corners are rounded and which are not. Additionally, they add an extra layer of complexity to the code (note: IE, please add support for border-radius).
As part of the effort to simplify our visual style, the design team recently decided to go back to our square corner roots. In doing so, we hope to champion cleanliness and the razor cut look that Facebook is known for.
That’s choosing consistency over the popular choice to go with rounded corners just because it’s a recommended design pattern. Not everybody would have the guts to do that.
Heck, it takes guts for Facebook to keep tweaking its interface, because at each turn it’s spurned so many protesting groups that keeping track of which one is against which feature becomes futile. For all we know, new groups protesting this rollback will surface yet again.
But Facebook always knows what it wants, it seems, and always sticks to its guns. Given the current design trends—from “Web 2.0″ gradients, candy colors, large fonts, and rounded corners, to Apple-inspired interfaces, to the highly detailed grunge and Victorian textures—would you, as a hypothetical head of the Facebook design team, have come up with something like its current look? Or would you have changed it? Save for the already-gone rounded corners, people wouldn’t have pegged this site for a spawn of the Web 2.0 era. It didn’t feel the need to look like one. Its features already spoke volumes.
Let’s talk feature redesign. The most controversial one so far, which put the status updates on the homepage, has also redesigned the social networking design pattern as a whole. It’s not just a copycat of the Twitter or FriendFeed (which it just acquired) interface, but emergence of the Real Time Web had a lot to do with it.
Back in the glory days of MySpace and Friendster, Facebook had a chance to copy its ability to ultra-customize profiles with custom CSS and background images. And there was a time when FB’s apps messed up profiles that things almost looked as horrible as any MySpace or Friendster page, but Facebook once again swept in and prioritized consistency. Over total freedom.
Facebook always seems to be choosing the unpopular, unconventional path, but it’s now the most popular social network on the planet, and the 3rd most popular site in the world second only to Google and Yahoo! They must be doing something right.
One of the most ambitious efforts to come out of the Googleplex (or anywhere, really) in ages is Google Wave, a real-time messaging, sharing, and collaborating service unveiled last week. Finally, Google’s crack at the Real-Time Web. We’ve been waiting.
Google’s Real-Time Web
You might recall ReadWriteWeb proclaiming the big G missed the boat on that, as Twitter rules over real-time search these days. However, Wave makes one realize there is more to the real-time web than 140-character messages.
It’s a new way of doing things. It’s decentralized, open-source, and poised to take over online communications the way email has, since it’s built as a fundamental protocol. But it’s not even just “the new email”, it lets you do a lot more than that. It was built to service needs knowing the capabilities of the Web today:
Ezra Pound once wrote: “”The artist is always beginning. Any work of art which is not a beginning, an invention, a discovery is of little worth.” And elsewhere: “Make it new!”
Even more than the application itself, I love the way Wave doesn’t just build on what went before but starts over. In demonstrating the power of the shared, real-time information space, Jens and Lars show a keen understanding of how the cloud changes applications.
When I saw Wave for the first time on Monday, I realized that we’re at a kind of DOS/Windows divide in the era of cloud applications. Suddenly, familiar applications look as old-fashioned as DOS applications looked as the GUI era took flight. Now that the web is the platform, it’s time to take another look at every application we use today, and ask the same question Lars and Jens asked themselves: “What would this look like if we invented it today instead of twenty-five years ago?”
This is not another reboot of the social network format the way Google redid email with Gmail and redid search with Google Search. But it does feel this is the way social interactions on the Web were supposed to be. Aren’t you tired of signing up over and over for the hottest new web service, OpenID/etc. not withstanding?
I love the diversity and downright chaos of the Internet, but the future has got to be seamless integration between all things. Text, photos, videos, blog posts, polls, calendars, petitions, lyrics, jokes, LOLcats, whatever.
Now when Google says real-time, it means your friend’s message appears on your screen by the character, instead of a “your friend is typing…” notice as you twiddle your thumbs. It also means you can reply to any part of your friend’s message, edit any part of a document, and replay exactly how everything happened when you’re done. See video above. It’s brilliant.
Terrifying ramifications?
That’s barely scratching the surface. I’m not sure if the protocol will succeed—not everybody lives in real-time online, or can handle this many features (see Twitter).
If it does succeed, it might become too successful that users are addicted, possibly trapped in this real-time space. We continue to blur the line between the real and the virtual, and even if at this point we can tell the difference between the two, will we ever reach the point of being “too” connected, transparent, hyperreal?
I’m not even sure if we should be trust yet another invention from Google—there has to be something in it for them, right?
Are you terrified yet? I think I am, but I’m pretty excited too.
Right now I’m listening to a live piano performance by Imogen Heap (she calls it “piano noodlings”) being broadcast over USTREAM, announced over Twitter a few minutes ago.
Several hundred other people are watching too, and it’s a new kind of musical experience thanks to the real-time Web. People have spoken of it before, and this is a fascinating aspect of it.
We can all sit down in front of the computer in our individual homes and listen to an Imogen Heap concert, live, together. It’s not quite the real thing, of course, but it’s different. Good different. It’s simple, spontaneous, and inclusive.
I can’t wait to see what other artists and other game-changers come up with in this next era of the Web.
*/
