App Config

App Config helps testers and developers switch an app’s environment without creating separate builds. It works with apps that include the AppConfig library and lets you point the same build to staging or production. However, the app under test must be registered in advance so App Config can access it. Using the App Config APK keeps the same configuration approach on any device during testing. This approach helps keep builds consistent across team devices.

App Config Features

Switch environments

App Config lets you change environment endpoints for your test app. Use the same build and select whether it should connect to staging or production. Settings apply through the included library, so your app reads the new values without a rebuild.

Library required

Your tested app needs to include the AppConfig library. App Config communicates through that library to read and update configuration values exposed by the app’s provider. If the library is missing, configuration changes will not be possible.

Register tested apps

App Config must know which app you plan to test. Due to package visibility limits, the tested app’s content provider authority needs to be registered in advance. Until automation is available, registration is handled manually by the maintainer. Align with your team to provide the correct authority, and confirm that you use the App Config latest version before starting a test cycle.

Open source code

App Config and its companion library are open source. You can review usage details and contribute on the project page. Visit the repository at github.com/PRosenb/AppConfigApp for documentation and updates.

Set up your tests with App Config

App Config helps you point the same build to staging or production during testing. Make sure your tested app includes the library and is registered before use. To begin, download App Config and follow your team’s setup instructions.