Cocoa touch framework avoid reverse engineering

As per this "It seems NOT to be possible to reverse engineer to Cocoa code."

Well, I disagree with that. Most security questions devolve into a cost/benefit analysis. How hard is it for an attacker to reverse engineer your code, versus what benefit do they get? The fact that Apple platforms use compiled code makes it harder to reverse engineer the code, but it’s certainly not impossible. You can take steps to make it harder still (like stripping internal symbols), but that only moves the balance point: It’s always going to be possible.

Which brings us to this:

Are there any apple standards or any other best ways to solve this problem?

Folks can talk, in general, about the cost of reverse engineering, but we can’t offer you any useful advice because we don’t know anything about the other side of the equation, the benefit. How much does an attacker benefit from reverse engineering your code?

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

ps DTS is closed 21 Dec through 1 Jan.

Maybe you should also consider this: if an attacker is able to decompile your code and reverse engineer, he is probably able to develop a similar code by itself.

Unless your code deos things that could turn dangerous to users if use unappropriately.

May be that is what you should consider: what the risk if evenr your code got tampered ? And then, how to mitigate this risk.