CODEWITHSUNDEEP
iostestflight
user996142
user996142

Reputation: 2883

Do I need TestFlight?

As I understand, TestFlight does 2 things:

I do in-home (enterprise) app and distribute it directly, with out of AppStore.

Looks like I do not need TesFlight, and may stay with adhoc provision and install app with our internal portal. Is it true? Does TestFlight have some special features I may need?

Upvotes: 1

Views: 176

Answers (2)

trojanfoe
trojanfoe

Reputation: 122391

Crashlytics

Pros

  1. Quick to release as no review process takes place.
  2. Integrated crash reporting and analytics's easily viewable using web interface.
  3. No limit on lifetime of beta cycle.

Cons

  1. Requires you to use a development provisioning profile, where every tester's UDID is known and added.
  2. Can be tricky to integrate frameworks into project.

TestFlight

Pros

  1. Uses production provisioning profile so no need to manage UDIDs.
  2. Release is integrated into Xcode with no 3rd-party frameworks.
  3. Crash reporting etc. Not sure about analytics.

Cons

  1. Slow (48 hours?) release time as goes through minor review process.
  2. App lifetime limited to 30-days per beta release.

There is no clear-cut winner and I went from Crashlytics to TestFlight as it was cleaner and I got to rehearse my release every single time I released a beta.

Upvotes: 1

Lucas van Dongen
Lucas van Dongen

Reputation: 9858

I like products like TestFlight and Fabric because they are bit easier to control and distribute compared to direct ad hoc builds. Specially when I add a new device to the portal it's sometimes difficult to see if that device is actually included in the build or not. With Fabric or TestFlight you have your users and your users have their devices. You can see which user has what device and distribute to a selection of users without too much hassle.

Upvotes: 1

Related Questions