If you think reverse engineering is a security threat, then your app was poorly written all along. Anything that's actually secure would remain so even if the entire source code were public.
Hi! We don't think that it's really true because a) open source != secure b) a good security is ALSO enforced by obscurity (which does not mean you have to build your cryptography stack on secrecy of course) but you need to prevent that people can do whatever they want with your application (and potentially your services).
E.g. most of the application you use daily have API and companies want to secure their API in a way to prevent misuse or abuse. How can you understand which request is good and which one is bad? You can build whatever system for rate limiting etc, but you should have a way to keep your data in your hand and block any attempt e.g. to collect data from bots.
E.g. most of the application you use daily have API and companies want to secure their API in a way to prevent misuse or abuse. How can you understand which request is good and which one is bad? You can build whatever system for rate limiting etc, but you should have a way to keep your data in your hand and block any attempt e.g. to collect data from bots.