Hey everyone,
I saw you use manual collection of UDIDs and then sending out notifications about the beta test. Have you thought about using a service like Testflight [1] where you can manage the beta testers (and their UDIDs) more easily, collect the UDID automatically and even notify the testers automatically if there is a new build for them? Actually, there are many more great features that I grew to love during my day-to-day work with lots of beta versions of different apps. Like for example the service being free.
(I'm quite new here, hope this discussion wasn't had before)
Regards, Jan
[1] https://testflightapp.com/
PS: No connection to Testflight, just a very happy user with our company.
On Thu, Apr 12, 2012 at 1:06 PM, Jan Piotrowski piotrowski@gmail.comwrote:
I saw you use manual collection of UDIDs and then sending out notifications about the beta test. Have you thought about using a service like Testflight [1] where you can manage the beta testers (and their UDIDs) more easily, collect the UDID automatically and even notify the testers automatically if there is a new build for them? Actually, there are many more great features that I grew to love during my day-to-day work with lots of beta versions of different apps. Like for example the service being free.
I believe we made an initial attempt to get stuff running via Testflight, but had some difficulties and put it aside. IIRC the most time-consuming parts of the process are still manual (adding UDIDs to the provisioning portal, creating an ad-hoc distribution provisioning profile, creating new profiles and new builds every time you get more UDIDs to add, etc). It does seem to have a way to *collect* UDIDs but we still had to do everything with them?
Maybe we were doing something wrong, I'm not sure... Possibly even if none of the UDID & key management is automated, it'd be a win for distribution once we figure it out vs sending files to people to stick in iTunes...
-- brion