The Battle of IDEs

Why to use Xcode instead of the Arduino IDE or any of the Processing-based Wiring-derived Arduino-like IDEs?

All the Processing-based Arduino IDE, chipKIT MPIDE, Wiring, LaunchPad Energia are great tools and provide plug-'n-play instant reward. 

However, 

• They are limited for library development and large projects: how could I remember the syntax of all the libraries I've developed?
  
• Why should I change the IDE when I take another board, provided the code is mostly compatible across all platforms?

OS X and Xcode

Among other concerns: a set of keys different from the Mac OS standards; missing features like auto-completion, parameter tool-tips, refactoring. Have a look at what Xcode brings.

Because I use Xcode on a regular basis, why not using it also for the embedded computing boards, as Arduino, chipKIT, Wiring and LaunchPad, Digistump, Teensy?

The major assumption is to consider the sketches as standard C++ code-sources.

embedXcode

The original structure of the makefile was limiting further development. Because it was based on the sole MPIDE application for both Arduino and chipKIT boards, new platforms couldn't be implemented.

A major revamp introduced a modular structure, with one specific makefile per platform. Now, embedXcode can handle Arduino, chipKIT, Wiring, LaunchPad MSP430, MSP430FR5739 and LaunchPad Stellaris, Teensy, Digispark boards with their corresponding Processing-based IDEs. 

Adding a new platform requires adding a new makefile specific to that platform. Learn how to add your board.