The deployment cycle of a mobile SDK is different than that of a mobile application – no matter how often and quick your release cycles are, you’re still dependent on the release cycles of the hosting app. This fact makes it harder to test and tweak your code based on production experience.
Configurable parameters to the rescue! Making your code configurable by adding parameter control from the server is not limited solely to the development stage of the SDK lifetime, it can be extremely beneficial in production as well. All part of the deal when you don’t control when new versions and code will be rolled out to users. So, while using configurations is a good practice for mobile apps and SDKS alike, for SDKs it can literally become a ‘make it or break it’ issue.
The basic need is for your code to behave differently based on server-side configuration. The configuration can include different behaviors for different customers, A\B testing, general parameters used throughout the code etc.
The implementation details can vary between different platforms, languages and use cases, but there are a few common issues to consider.