3 ms·
Well, I think from a customer point of view they see "making things more stable/reliable" as "no progress". Customers, rightly so, expect things to be stable an
by dfj225 16y ago
Well, I think from a customer point of view they see "making things more stable/reliable" as "no progress". Customers, rightly so, expect things to be stable and reliable from the start. Otherwise, they are testing your product and not every customer wants to do that.
I feel like Twitter was very lucky that they did not see a decrease in use and adoption while they had many problems with scaling.
- rythie 16y agoI think Twitter benefited from having no attractive competition during that time (mostly there were similar sites, with little innovation and few users). Also I think you get a 6-9month grace from early adoptors while they can see you scaling up staff and getting funding. However, after a certain point they start putting up blog posts about the lack of progress and pointing out alternatives. I think this is partly because it takes a while to get really used to what your app. does and how it's useful to them.
- dfj225 16y agoYes, Twitter was lucky in more than one way. I agree with what you said about early adopter. I'd label these people as "willing to test products", even if that means they will encounter some bugs or issues. However, not every business will be able to say that about their first set of customers.
- mlinsey 16y agoI think the biggest benefit for Twitter was that thanks to their API there were developers working on improving an innovating on top of the product even when Twitter was focused entirely on scaling.