As developers ourselves, we get excited when our products go into production and people start using it, but at some point we notice that that important red button we want users to tap so badly is not being tapped as we want to. This can be a problem because that button has a purpose for us, and if users are not interacting with it, we might not achieve, for example, enough sales. As a solution for the problem, we might have some ideas to test out, but making users download new versions for each solution we consider might become a hassle for them, and even cause us to lose more users in the process, and we don’t want that to happen. As a solution for this problem, we want an option that allows us to generate metrics for each idea we want to test with the users without them needing to get a new version. This can be done using A/B testing and Remote Config with Firebase. Expect to come out of the session with: An overview of what A/B Testing and Remote Config is Why, When and How to apply concepts those into your project A working implementation on our application and expect some great results afterwards.