How to ensure the security of the mobile SDK when transferred to third parties?

Question

Mobile development

There is a task to provide partners with an SDK for mobile development. But at the same time, I really would not like the source code of the SDK itself to be available, i.e. it is necessary to give blackbox with documentation to it.
I ask you to share your experience of implementation, the pros and cons of this approach.
It is quite logical to use code obfuscation, but is it possible to give the SDK in an already built format, and not in source codes, even obfuscated ones?

Answer 1

What is SDK written on? In general, you can assemble it into the library of the target platform (jar for android, for example) and give it away. The possibility of decompilation will still be, but strictly speaking it is always there.