We don't think of it as an either/or (In fact, buddybuild supports deploying directly to Testflight as well).
Buddybuild's deployment really comes into its own earlier in the dev cycle
- when you want to deploy to your internal team (who might want to jump to old builds or different branches)
- when you want to schedule deployments (every evening for example)
- or when you want to send a build very quickly to someone.
We've made the onboarding experience for new testers very simple - automatically handling adding UDIDs to provisioning profile. Also, not having to install a separate app is very appealing to some people.
Buddybuild's deployment really comes into its own earlier in the dev cycle - when you want to deploy to your internal team (who might want to jump to old builds or different branches) - when you want to schedule deployments (every evening for example) - or when you want to send a build very quickly to someone.
We've made the onboarding experience for new testers very simple - automatically handling adding UDIDs to provisioning profile. Also, not having to install a separate app is very appealing to some people.
We show off that part in our demo : http://www.buddybuild.com/demo
Testflight works really well for very large external test groups.