ITUNES CONNECT CODE

As has happened in the past, there have been times our workflow has fit directly into AppleвЂ™s vision, there has been times where a little more work was required, and there have been times where we have been forced to change our workflow. Hopefully, many of those improvements will address different types of companies and different workflows. So, it stands to reason that Apple is already working on improvements and additions to this process of deploying to internal and external testers, and to the App Store. This applies to SDK developers even moreso: an early, ugly API decision can cause problems for years for many, many developers.

As we become more comfortable with the problem and its solution, we can craft a more appropriate API for that solution. Our first shots at solving new problems are often ugly. Of course, many of us knew then what most folks know now: private APIs are often the beta version of what will become a public API. The argument was often that Apple was being anti-competitive and screwing the little man, pre-emptive Sherlocking, if you will. (In general, at least everyone is allowed to make mistakes.) For example, it was only a few years ago when a private API that Apple used in one of their applications was a cause for protest.

This has been my experience with Apple as a developer over the last decade: Apple waits until things are well-polished and tested prior to release. IвЂ™m assuming that weвЂ™ll see more and more functionality rolled into TestFlight.

ITUNES CONNECT CODE

Other improvements to the rest of the process for code signing and distribution system have been welcome as well вЂ“ I rarely have to go into the developer portal and manually enter things these days.

Since switching over to AppleвЂ™s TestFlight, weвЂ™ve been pretty pleased.В The clear versioning of applications, easy internal and external test distribution, and having App Store distribution hooked into the same system is actually really great.