[英]Do I need TestFlight?
As I understand, TestFlight does 2 things: 据我了解,TestFlight做两件事:
I do in-home (enterprise) app and distribute it directly, with out of AppStore. 我做家庭(企业)应用程序,并直接在AppStore外分发。
Looks like I do not need TesFlight, and may stay with adhoc provision and install app with our internal portal. 看起来我不需要TesFlight,并且可能会保留临时设置并通过我们的内部门户网站安装应用程序。 Is it true?
是真的吗 Does TestFlight have some special features I may need?
TestFlight是否具有我可能需要的某些特殊功能?
I like products like TestFlight and Fabric because they are bit easier to control and distribute compared to direct ad hoc builds. 我喜欢TestFlight和Fabric之类的产品,因为与直接构建相比,它们更易于控制和分发。 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.
使用Fabric或TestFlight,您可以拥有用户,而用户也可以拥有设备。 You can see which user has what device and distribute to a selection of users without too much hassle.
您可以看到哪个用户拥有什么设备,然后毫不费力地分配给选定的用户。
Pros 优点
Cons 缺点
Pros 优点
Cons 缺点
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. 没有明显的赢家,我从Crashlytics转到TestFlight,因为它更干净,每次发布Beta版时,我都要排练自己的版本。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.