3 ms·
When I think about social software (which is the context in which "virality" lives, anyway) I think you have to build for three things - in this order: 1. Util
by joshu 18y ago
When I think about social software (which is the context in which "virality" lives, anyway) I think you have to build for three things - in this order:
1. Utility - it must be high utility, even if nobody else is in the system.
2. Network Effect - As people are drawn into the system, it needs to scale in value more than linearly
3. Residual value - Value taken out of the system, sometimes as revenue. Typically ads.
I think that it's not good enough to do these alone, however. You must construct something that isn't just viral but that makes it such that the fact that some person is not on the system is PAINFULLY ANNOYING to the actual users of the system. Consider the growth of email, in general: "Please just go sign up for an email address somewhere so I can email you!"
If you construct it in this manner, you do not have to spam people. Delicious, which has a lot of users, never emailed anything other than password resets, for example.
- pclark 18y agoHow did delicious get momentum in terms of user base? Did you do anything in particular or did you just solve a problem and voila?
- joshu 18y agoI used the predecessor to delicious, alone, from 2001-2003. Then delicious took another two years, 2003-2005 to get to tens of thousands of users. So it took a really long time. Firefox extensions and RSS helped a huge amount. And it was close to one of the first user data sites that had an API (before Flickr, I think...)
- pclark 18y agofascinating - thanks. I think in 5 years time delicious & flickr will probably be the two webapps i still use.
- netsp 18y ago1. Utility - it must be high utility, even if nobody else is in the system. Doesn't this simply exclude some domains. email, facebook, dating sites. Are you suggesting that these domains need to be approached by inserting some basic (slightly unrelated) utility that is useful without other people?
- joshu 18y agoIn an age where those things already exist, it's very, very difficult to bootstrap.
- netsp 18y agoSorry. I think I was unclear. I was just trying to demonstrate pieces that live in the "social software" space which would be difficult to build while conforming to the rule. I suppose it would be possible, but it would be a squeeze of some sort. I could imagine Skype starting as a phone book or email starting as a way of organising your faxes for the day, but it seems hard. Say you've made skype. It's really good at being a phone, but it needs more people signed up to become Skype. Now you decide that in order to make more people sign up, you should make it into a great phone book. A lot of people might want to use a desktop phonebook already. If you made a really good one people would use it & once some of their friends used it, they could skype call each other too. The problem I see with this idea is that you need your Skype to be a good phone & a good phonebook. If we're talking 0 cost, it probably needs to be the best at both. Being the best at anything is hard, two things is really hard. BTW, I'm not really against the idea of utility. It's a way of cracking the chicken-egg problem. But would you discount the other ways?
- joshu 18y agoI never really said it's a rule. It's the way I think it generally needs to be done. Obviously, there are exceptions. Skype did not evolve in a vacuum. It piggybacked off the phone system. "Make calls for cheap" - which is a direct call to utility. Remember that any system that gets its users laid or makes them money can have the users jump through hoops to use it. Anything less than that has to have increasingly more finesse.
- netsp 18y agoI'm going to paraphrase, so I apologise in advance. Remember that any system that gets its users laid or makes them money can have the users jump through hoops to use it. Anything less than that has to have increasingly more finesse. Could I distil this to: "Skype got away with not having this because.."? BTW, I'm not saying that creating something that is useful without a network is bad. It's good. I'm just saying that in many cases it's very hard. Say skype had gone down this path. They may have failed to find some way (eg phone book) of making it useful to just one person. Forcing the approach seems like unnecessarily inserting a another binary hurdle. On the other hand, the slightly less elegant approach of getting your small number of users that want to save on phone bills to nag their friends seems more suitable. The existing users have in-built incentive to do this. It's pretty much guaranteed to produce some results.