[Vincent Ferrari]

http://www.mobileorchard.com/6-tips...ur-app-noticed/

"Getting app reviews is part of a larger category of getting your app noticed. This article, expanding upon and broadening the earlier piece, provides six straightforward ways to get your app some attention."

Oddly enough, they missed one very obvious way: don't be afraid to give away "review copies" to sites that write about apps and such.  It only makes the connection to the product stronger for people who read those sites.  If you pass on it, you're passing on a very easy way to get some free publicity.  They kind of hint at it in number 3, but it's more than just a press-release thing.  Give away copies.  Most sites, when presented with a free copy of software, will happily review it (unless of course you're a site like Engadget that gets thousands of things to review every day).

I think the best tip of all the ones given, however, is number 6.  Nothing says "I'm listening" like a responsive developer who incorporates user suggestions into the final product.  I've been lucky enough to meet a few of them as Executive Editor here, and it really proves to me that they care about their product enough to not be stubborn about it.

Any of you folks out there have an app you've developed, by the way?

[Vincent Ferrari]

http://www.mobileorchard.com/6-tips...ur-app-noticed/

"Getting app reviews is part of a larger category of getting your app noticed. This article, expanding upon and broadening the earlier piece, provides six straightforward ways to get your app some attention."

Oddly enough, they missed one very obvious way: don't be afraid to give away "review copies" to sites that write about apps and such.  It only makes the connection to the product stronger for people who read those sites.  If you pass on it, you're passing on a very easy way to get some free publicity.  They kind of hint at it in number 3, but it's more than just a press-release thing.  Give away copies.  Most sites, when presented with a free copy of software, will happily review it (unless of course you're a site like Engadget that gets thousands of things to review every day).

I think the best tip of all the ones given, however, is number 6.  Nothing says "I'm listening" like a responsive developer who incorporates user suggestions into the final product.  I've been lucky enough to meet a few of them as Executive Editor here, and it really proves to me that they care about their product enough to not be stubborn about it.

Any of you folks out there have an app you've developed, by the way?