How to ensure mobile security SDK when transferring to third parties?
There is a challenge to provide partners with an SDK for mobile development. But I would not like to see the source code of the SDK was available, i.e. it is necessary to give blackbox c documentation.
Please share the experience of implementation, pros and cons of this approach.
It is logical to use the obfuscation code, but is it possible to give the SDK in assembled format and not in the source code, even obfuscated?
Ana.Hagenes18 answered on September 18th 19 at 23:42
What is written in SDK? Generally can build it into a library target platforms (jar for Android, for example) and to pay for it. The possibility of reverse engineering will still be, but strictly speaking it is always there.