Xcode is an IDE used to develop, test, and distribute apps across all Apple platforms, featuring Swift and SwiftUI with a multiplatform app experience, enhanced editor features to help users code faster.
This is almost not a case of Xcode being the 300-pound gorilla in the space, but of it being essentially the ONLY viable gorilla in the space. There are other text editors, of course, that can be used for coding; and in some cases other IDE's might make sense for a cross-platform development scenario, but since this is Apple's in-house tool, fighting against that flow is just going to be an exercise in frustration. And, if you need help from Developer Support, they are going to be most familiar with Xcode.
Over the course of months/years, various security exploits and other issues are discovered and patched in AIR, often requiring you to rebuild and resubmit mobile apps to the various storefronts. This happens often enough that it's worth mentioning as a major con.
While development on Adobe AIR seems to be fairly constant, there is very little communication between the community and Adobe regarding the future and general support of AIR. The track record of Flash (and particularly Flash Mobile) does not inspire much confidence that Adobe intends to support Flash/AIR for years to come.
Adobe AIR does not seem to perform as well (in terms of raw performance, memory usage, framerates, responsiveness, etc.) as other hybrid solutions for certain tasks. For example using shaders tends to be experimental still, and graphic/animation intensive projects often require the use of third party frameworks such as Starling.
Although Adobe AIR is just an SDK without an actual "UI" it's commonly used within Flash, Flash Builder, or FlashDevelop. Considering the integration with Flash IDE, there are very few tools that can compete with its features.
Xcode occasionally exhibits some behaviors that are hard to explain, but are generally cleared by restarting the program. In an application this large and complex, I suppose this is somewhat expected. The sheer vastness of the frameworks collection has to be a huge management issue all by itself. However, those breaks in the flow can have impact on developer productivity.
Since we don't use the cloud based features of Xcode, it is basically available 24/7 for us. We don't need the extended compilation features that are offered in the cloud as our projects to this point have not been that large or complex. We have never seen a wholesale breakdown of Xcode availability at any point in our use of the product.
Every developer wants faster compiles, but that can be achieved by either going to the cloud or by provisioning the local station to a higher powered configuration. My only minor complaint is the amount of local mass storage that Xcode as a system consumes. This makes it interesting to set up a development environment on a midrange laptop, however it is easily managed with external storage at a reasonable price.
Originally, Adobe AIR was the only game in town, and its blend of flexibility in platforms it could publish to (PC, Mac, iOS, Android), ease of use, and familiarity made it the clear choice. Now Adobe no longer supports it, and we’ve found the transition to Harmon unworkable for us.
Xcode is a much easier to use and full featured IDE than many of the competitors. It also is a way better experience to use. Much better looking in general
Xcode only loses points due to the occasional situation where it manages to somehow tie itself into a knot and starts to exhibit odd symptoms. This is almost always solved by simply saving progress and restarting the environment. Fortunately, that doesn't happen too frequently and is easily repaired while taking a short break to walk around and stretch.
