Just as Windows is different from Mac OS X, so too are the phone environments that we use every day, both from a users standpoint, and from a developer’s standpoint. This series will take you through some of the differences with Project Manager, Peter!
When we’re ready to start distribution for testing, we must go through a few special steps. Since Apple has limits to how many devices you may internally test on, we must register those devices to the Apple Developer Account being used for distribution.
To help us automate that process, we will use a service called TestFlight. Before testing begins, we will need a list of emails for users who will be testing the iOS app. We will invite those users through TestFlight, where they will be asked to register a device. It is significantly easier to do this process from the device you will be registering, as it will automatically register the device from the email.
Once everybody has registered a device, we will collect the Unique Device Identifiers (UDIDs) from TestFlight, and add them to the Developer Account. This will then allow us to create a provisioning profile, which will be used to build the app. This process must be done every time a new Device is added, so it’s beneficial to make sure all testers are registered before we send the first test build. When we are ready, TestFlight will send out an automated email with install instructions for the build.
Yet again, Google makes things easier for Android users. Since there is no device limit per account, we’re able to freely distribute the app to whoever intends on using it. This will be done by sending an email with the .apk attached to testers, who can directly install the .apk from the device.
Download the full resource here. It includes:
- and Testing