

Developers commonly use dummy images or data during testing. This is one reason why we should use separate servers and databases for different environments. The development version of an app typically uses a different database (or other systems such as analytics) from the production environment.
WHAT IS AN XCODE TARGET SOFTWARE
Standard software development practice is to use different environments for the different versions of the software, and in our case, iPhone apps. The reason is because as you continue to build new features or develop your app, you want to separate the development version from the existing public production app.

This sounds good, right? But instead of changing the values back and forth between the development and production environment, is there a better approach to handle both the development and production builds? This is exactly what Eugene is going to discuss with you.įor starters, some of you may be wondering why you should use two separate databases and environments while developing your app. Before submitting the app for Apple’s review, you’ll need to modify all these API keys and URLs to fit for production. The problem is that some of the web service URLs are pointing to the testing servers, and the API keys are configured for the test environment. Imagine you’ve completed the development and testing of your app, you’re now ready to submit it for production release. Editor’s note: This is a guest post contributed by Eugene Trapeznikov.
