Simple conclusion: take advantage of the technical solutions Bootstrap provides and ffs put some work to make it look at least a bit original and branded.
Simple conclusion: take advantage of the technical solutions Bootstrap provides and ffs put some work to make it look at least a bit original and branded.
Different- for- different's- sake is a curse on web developers; it costs more time, more momentum, and more initiative than any other issue I can think of. Get the value working and proven first, then, when people are paying for it, start thinking of how much you'd budget to make your application visually distinctive.
There are exceptions, but they tend to prove the rule.
Today. The more people use raw TB the faster that 80% approaches zero and you'll get to my conclusion.
You will probably not pull off the next Foursquare or Pinterest using Twitter Bootstrap. But: you're not going to pull off the next Foursquare or Pinterest anyways.
So think of it this way: this debate has the question backwards. If you're doing a startup for which a major risk of your version 1 is that you built it with Bootstrap, you probably picked a bad startup idea.
I run a little marketplace for Bootstrap themes called WrapBootstrap - http://wrapbootstrap.com/ - I just sold the 100th theme today so more people are taking customization seriously within the Bootstrap community than before.
You can also check out Bootswatch - http://bootswatch.com/ - He provides free color themes that you can use to skin Bootstrap with.
People should definitely be using Bootstrap for its technical merit and not for its default styles.