Need advice about which tool to choose?Ask the StackShare community!
CLion vs Xcode: What are the differences?
Developers describe CLion as "A cross-platform IDE for C and C++". Knowing your code through and through, CLion can take care of the routine while you focus on the important things. Boost your productivity with the keyboard-centric approach (Vim-emulation plugin is also available in plugin repository), full coding assistance, smart and relevant code completion, fast project navigation, intelligent intention actions, and reliable refactorings. On the other hand, Xcode is detailed as "The complete toolset for building great apps". The Xcode IDE is at the center of the Apple development experience. Tightly integrated with the Cocoa and Cocoa Touch frameworks, Xcode is an incredibly productive environment for building amazing apps for Mac, iPhone, and iPad.
CLion and Xcode belong to "Integrated Development Environment" category of the tech stack.
Some of the features offered by CLion are:
- Smart Editor
- Code Generation
- CMake
On the other hand, Xcode provides the following key features:
- Source Editor
- Assistant Editor
- Asset Catalog
"Good editor" is the primary reason why developers consider CLion over the competitors, whereas "IOS Development" was stated as the key factor in picking Xcode.
According to the StackShare community, Xcode has a broader approval, being mentioned in 1051 company stacks & 603 developers stacks; compared to CLion, which is listed in 9 company stacks and 8 developer stacks.
What is CLion?
What is Xcode?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Xcode?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using CLion?
What are the cons of using Xcode?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with CLion?
What tools integrate with Xcode?
Sign up to get full access to all the tool integrationsMake informed product decisions
I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.
The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/
SmartZip
As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.
Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.
Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.
After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.
After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.
Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.
XcodeEven though React Native takes care of most of the heavy lifting, there are still some cases where we need xcode. These cases include app icon integration, mobile deployments, loading screens, ect...
CLionCLion is used to build shiro.
It is the primary IDE for development on shiro and the source control repository comes with predefined scripts for easy development and testing of shiro.
XcodeXcode is our primary development platform for iOS applications, with a very fully featured set of dev tools for the platform. For everything else, there's Sublime Text 3.
XcodeExperience with Xcode in the context of iOS development. This includes Storyboards, Debugging tools and the Simulator.
XcodeQA and Testing have been so much easier with the help of its simulators on Apple Devices like; iPhones and iPads.
XcodePrometheanTV provides SDKs for IOS devices and utilizes the XCode IDE for development and testing purposes.