No matter how smart people are and how much time and resources we have things can go wrong in any project. And the bigger the project becomes the more needs for configurability emerge. These needs can be fairly basic from turning off unfinished features in the release branch to allow teams to work and integrate faster. To support a multitude of different behaviors in similar applications in different countries. If we look carefully we will notice that almost any project has some sort of configurability mechanism.
In this talk, we go through the myriad of configurability mechanisms such as static release constants, flavor constants, feature flags, operational feature flags, and a/b tests. We will also dive deeper into the underlying implementations of these mechanisms on mobile. We will see on the real life examples how these simple mechanisms could save us from vital mistakes and overall improve the development process.