AppCode vs Xcode: A Comparison of Swift Package Manager

For the past few years, Swift Package Manager has been handling dependencies seamlessly. However, some users have reported issues with slow project launching and horrific remote dependency resolving outside of indie development. In this article, we will delve into the differences between AppCode and Xcode in terms of Swift Package Manager, exploring possible causes for these problems.

One aspect that may contribute to these issues is how Xcode is used. Some developers have reported that using pure code without XIBs or storyboards can lead to slower project launching times. Additionally, avoiding SwiftUI for complex projects and writing Swift in a style that avoids common coding mistakes may also impact performance.

In contrast, AppCode has not been plagued by these issues. In fact, some users have reported no difference in their app's performance after switching from Xcode to AppCode. With over 50 apps in its catalog, one developer has confirmed that all of their apps launch super fast.

However, remote dependency resolving remains a significant issue for many users. This is particularly problematic outside of indie development, where complex projects require multiple dependencies. To mitigate this issue, some developers have implemented build scripts separate from Swift Package Manager.

Another potential cause of these problems is the lack of basic build settings with Swift Package Manager. Additionally, integrating test plans into SPM can add 4-10 minutes to CI builds.

For those experiencing these issues, it may be worth revisiting their project setup and exploring alternative solutions. Meanwhile, AppCode remains a viable option for developers seeking a more streamlined and efficient development experience.

Appcode vs xcode