The questionable value of the real-time web - Demand-side attention economics
danieltenner.com
danieltenner.com
But It's importance cannot be underestimated. In a better world, augmented reality allows us to explore a reality with multiple layers and always contextually relevant information.
With that in mind though, the current state of RTW is the stone age and we are nothing but a bunch of slaves ploughing through an overwhelming amount of information in order to find something of importance that we can then share with others through some aggregator.
In a better world, we will still receive way to much information to ever process. But instead of scanning each post as a separate entity, the RTW will reflect an emerging alternate reality based on knowledge our needs.
Until then RTW will continue to include more and more sources communicating most of them automatically, but my guess is that they will be part of a soup of the augmented reality universe and serve to in the end create an alternative matter based on information. Allowing for the construction of the agumented layer.
There is huge start-up potential to figure out a way to filter information in a way that allows for all sorts of information to pass through without any of it being more important, but where it together will create an alternative reality.
I would think that the next feature that aggregator will need to look at it a better filtering only surfacing things to me when they are of importance (again exactly like the brain works)
Sorry for the rant.
The point about the term becoming muddled and meaningless is pretty spot on. When I first started hearing this term being used all over the place (heck, Toronto's already had a couple mini-conferences laced with this buzzword), I assumed we were talking about systems with "real time" data flows like Pachube.
Now the term seems to have boiled down to "I taped my F5 key down".
Surprisingly, the only exception to that is probably FreeNode IRC , certain channels at least.
Yes, there are certain bloggers i want to read, certain discussions on HN that i want to participate in but it takes time for me to assimilate and understand what is going on, the RTW doesn't help me there.
More generally, if I want to know what now is happening about something, twitter can usually deliver that.
There, you have used Twitter in the fashion of the "traditional" web, you just went to a RTW source thats all.
My point is i generally don't have any use for what "now" is happening, anything that is of importance generally has a longer time span and relevance to me and i don't "need" to know it straight away.
We're not used to having down-to-the-second real time search yet, so it's harder to come up with use cases until we really become comfortable with these new systems. Most use cases we do see, like Trending Topics on Twitter, are discovery queries that will eventually be covered by Google's spidering, but there are whole categories worth of search cases in the long tail that won't be covered by just discovery.
Other uses might be traffic information, black-friday sales, tornado tracking/response, stock trading, organizing and coordinating civil protest, and rapid response for brand managers.
For example, I play fantasy football and I noticed during Sunday afternoon that Kevin Smith (Lions' RB) suddenly stopped scoring me points. Did he get injured? I don't have cable & Google's "recent results" showed nothing... so I performed a Twitter search for his name and my worst fear was confirmed by dozens of Lions fans on Twitter: he was out with an injury.
The result of my search wasn't desired, but the "real-time web" was the only place to get the info.
Our project was to migrate all apps to a new real time package. They spent millions of dollars and when it was all done, the controller complained, "Who decided that we needed real time Accounts Payable? Why would we ever want to pay our bills faster?"
No one had ever asked that question before. No one even thought about it. We had spent $1 million on a module nobody wanted because IT decided it. Eventually he added procedures to continue to fill out all accounts payable transactions with pencil and paper and enter them into the on-line system at the end of the day. What a waste.
Same argument here. Some things you want faster. And you're willing to pay for them, one way or the other. But other things should just stay the way the are.
Some things never change: you actually have to think about your apps before you implement them.
Question for you, how did IT sell this to the business folks (or the buyer)? Was this under the auspices of enterprise agility?
Exactly. If a customer called in an order at 6:30 a.m., it didn't even get to the data base for 18 hours. So there was no same day shipping and if it had to be scheduled, the schedulers weren't even aware of it until the next day. Real competitive disadvantage. Worth spending millions to solve.
Real time Accounts Receivables paid for itself by reducing Days Sales Outstanding by one day. But real time Accounts Payable? Made no sense.
The IT solution was a blanket decision made multiple levels (and cities) away from the people who actually did the work. Go figure.
Its pretty inane, as you point out, how companies blindly apply strategies. Alot of times this is caused by simply cutting corners. If they would have had a body write up requirements (even high-level) for each department the would have caught this.
Were there any problems with the actual implementation? If there are these kind of problems at the architecture level, I can only imagine the issues that came up actually initiating and executing the program.
Twitter didn't have any info on Flight 1549 for a minute or so. In fact, the real time Summize search engine backend - seemed to be lagging in its indexing that morning. CNN and the other news networks were still reporting the same political/celebrity news of the moment.
Personal word of mouth just barely beats Twitter for real-time* information but it's very close. It's true crowd-sourcing (though questionable why people will tweet they are in an earthquake while it's happening - and not be safer).
* - My hardware/software RT engineer friends scoff at the mis-use of the RT term.
This looks like a common knowledge to fight distraction, but anyway: I currently experiment with email notification, and I start to reconsider using it again. The point is, that the small blurb doesn't actually distract me that much, and I immediately see that nothing important is coming, and as a result, I doesn't have an urge to check if some important email didn't come. And if something important came, I just know that immediately.
This article seems to say it's about immediacy, about finding out things faster than you would have before.
I've also heard that the real time web acts as a filter for news, so you can use the people you follow on twitter or your facebook to find out what information is important.
I know a lot of people on here are working on real time apps...what do you think that value is to the consumer?
The result isn't even close to what you want--the real time web will be a good thing.