For starters, some of you may be wondering why you should use two builds while developing your app. The reason is because as you continue to build new features, you want to separate the development version from the existing public production app. Standard software development practice is to use different environments for the different versions of the software. The development version of an app typically uses a different database and server from the production environment. Developers commonly use dummy images or data during testing. In testing or development environments, it’s not uncommon for one to use test data such as “test comment”, “argharghargh” and “one more test comment”. Obviously, you don’t want your real users to see this kind of messages. In the case, if your app using an analytics system, you may even send thousands of events during the testing stage. Again, you don’t want to mix the test data with the production data in the same database. This is why it’s always recommended to separate the development and production builds.
ios
There are 12 posts filed in ios ( this is page 2 of 2).
Distributing iOS application for testing and debugging
During development and testing of mobile application, we need to regularly send application build for tester or client for verification or work. So it very important to get familiar with number of ways to distribute your iOS application. In this article I will list out 4 such method.
- Distributing simulator build for other mac user with Xcode 6.0 or above.
- Wireless Distribution via www.diawi.com.
- Wireless Distribution via self hosted site.
- ipa Distribution.