Xcode

When artificial intelligence is absent from the integrated system, the swiftly advancing user is left with no alternative but to engage someone to undertake this particular facet of application development. The concept of drag-and-drop functionality reigns supreme among such users, and the absence of this feature leads to the attrition of a user. The implementation of this functionality is akin to releasing a floodgate upon the world, with numerous individuals eagerly anticipating new avenues for engagement.

It good but me want more you no good if think bad I will angry and sad I angry you mean person

Still non-stop issues using SPM and switching projects. Get stuck for 30-60 minutes at a time just trying to get SPM to load the packages correctly at times. Watch building and linking to device never works correctly. Makes development for watch very difficult when dealing with any BLE libraries. Please work on tightening up these areas before putting more effort into Apple Intelligence. It’s like Apple never reads any reviews for Xcode because these same pain points seem to never improve year after year after year.

genuinely think it’s a scam. here I am, the very weird dude at the coffee shop who approaches you when you’re clearly in your phone, to tell you about it: At some point, Apple realized they could slow the development of all competing products by simply provisioning, with first-class accessibility & visibility, something which would be ignorantly presumed to benefit from vertical integration. it’s an absurd hog of memory and CPU. It is extremely slow to perform extremely simple tasks. There is no doubt that this thing is running extraordinarily inefficient algorithms on extraordinarily bloated & numerous subjects. you actually just can’t use it for a moderately complex project unless you’ve got an M1 and even then you’re going to be dreading your work unless you are strategically working against it’s own habits. Nothing can or will be done without extensive pigeon-holing to ensure your previews are encapsulated enough to be updated in reasonable time. I think there is other evidence that it is an attempt at sabotage - xibs, storyboards, schemes and targets. The confusion of natural ideation with the actual mechanics of putting text onto a page, or with putting text onto a page with the creation of views, or of settings for building with settings for how a build will be used - in a manner that is so oddly antagonistic that you’ll wonder what genius designed such an opponent. it’s rly something. I recall as an undergrad texting a friend “this is great!!!” about Eclipse in 2013. I was just about to discover RStudio, Emacs, and VSCode. I was about to become a programmer who understood how valuable IDEs could be. I did not even know how good I had it. Somehow, in 2025, I’ll be using a tool which is vastly inferior to most open-source tools produced by the most valuable company in the world.

Not only does Xcode continue to be incredibly user un-friendly, but new versions get forced onto users with absolutely no warning that it will break compatibility. It’s as if the development team has no clue what it’s actually like to be a software developer. They are in their own little bubble completely oblivious to the negative impact some of their decisions make on the world.

When will you fix the log filtering bug? This is the worst compiler I've ever used, bar none.

I've always had a love-hate relationship with Xcode because it never seems sufficiently adaptable to use for c and c code. Objective-C seems kind-of inflexible and only almost-but-not-quite portable to servers so the code is less portable than one would wish. I always end-up using the command line or a better IDE for those projects and ones using JVM languages. Apple could learn a lot from JetBrains or the Eclipse foundation about how to accommodate a broad set of requirements.

work well

As an iPhone and Android developer, I am very familiar with Xcode and Android Studio. I think the most useful review is one comparing the two. Compared to Android Studio, Xcode needs constant updates to run, requires more memory, and is miserably documented. Every time I need to issue an update to an iPhone app I am disappointed, because it requires firing up this app, being told I need to waste hours updating before I can do anything, and then fixing the inevitable incompatibilities that arise. I wish I could use anything else… but of course, Apple is a closed ecosystem so we’re stuck with whatever they decide to put out. Always frustrating.

I’ve been using Xcode since 2002. It’s sad to see how the app has stagnated. Things that have been bad or broken from the beginning times of the app store, like device provisioning, have been made better but still far from good. I can’t provision my Apple Watch no matter that I try. The build settings are still a disaster. Yes they have added a bunch of nice GUI on top of entitlements. However, try to figure out why the API doesn’t work with your current device. File handling still doesn’t make much sense. Folders can be real or not, in several ways and those details mater since, they effect how things are compiled. Don’t get me started on Swift dependencies. XCode is trying to do too many things and serve to many different needs, and fails at most of them. Trying to get any thing fixed by filing a Radar is incredibly frustrating. It’s just a black hole. Unless you join the company and look up the Radar from inside any find it duped with 107 others and makers “will not fix”.