Re:Ask HN: Review my startup, http://conweets.com
by foxhop on Sunday July 15, 2012 @07:00PM
(#4248462)
> Your super-effective caching engine, described with words like "query" and "request" and "server" and "cache", is not relevant to your users. Like, at all.
I agree totally. In my marketing copy on LinkPeek I attempted really hard to stay away from the term API even though that is what the service is. Basically you must describe the product like your real customers would describe it.
Re:Ask HN: Review my startup, http://conweets.com
by ayushchd on Sunday July 15, 2012 @07:01PM
(#4248465)
Your advice about fonts and texts is certainly correct. I am working on it straight away. About the aggregator thing, yes I am working on it, but we do have a "trending" conversations section, but it isn't very dynamic because of less traffic.
Second, you should know that this has been done before, most notably probably by Bettween, which ultimately failed. Do people really have the problem of tracking conversations on Twitter?
Note that Bettween had a pretty effective marketing tactic that you could steal: finding really interesting conversations and promoting them, so that their site functioned both as a sort of Twitter aggregator (key function of an aggregator that you don't have: most interesting stuff bubbles to front page) and as a vector for sharing conversations in places like HN, which spread the Bettween app around.
Your super-effective caching engine, described with words like "query" and "request" and "server" and "cache", is not relevant to your users. Like, at all. Try to develop an allergy to describing technology. If the benefit of some technical feature you build is "speed", then just say your site is super-fast. Don't waste time justifying it. Does that turn a whole paragraph into a 5 word sentence? GOOD. Users don't like reading your marketing copy.