> Guys, how do you figure out the weak points of your application that led to rejection? Is there a way we can get a feedback on the areas we need to improve.

To be able to make a claim of originality, the developer should figure out how to improve his product without anyone holding his hand. If on the other hand a specific reason for rejection were to be given, doesn't the critic have the right to benefit from the fruit of his free engineering advice?

People end up liking new, innovative products for reasons they may not fully understand. Rejection should play by the same rules.

> ... but without a feedback it's really difficult to understand why the application was rejected.

Yep. Just like real life, where individuals sort out reality on their own.