Choosing a protector

again, another wrong way to think about protection. don't ask 'will this protector be better than another' cuz the truth of the matter is if the protector is interesting enough to catch someone's attention (along with your app) then it WILL be cracked, unpacked, whatever. try as you might, you are NOT gonna keep your app from the hands of and experienced reverser. that's just a fact.

what you should be looking at is the best balance of ease of implementation along with the best possible protection. in other words, think of your customers/potential customers. don't use a protection that slows down your app! if you used asprotect correctly and properly encrypted 'registered only' functions you'd be better off. and even then, if your app is desireable, chances are it will simply be subject to credit card fraud just to get all the locked up goodies.

again, cuz it seems that it can't be said enough, stop worrying about reversers, cuz you're not gonna stop them. think about how to make using your app an enjoyable experience for your customers.