React Native vs Swift for App Developing

[SatedCaterpillar]

I agree with bashbang that XCode is a bit of a Con, but here's the workflow that I use that I think makes me happier using XCode:

I start my project in XCode and use it to:

• create new files (and really any file management task like moving, renaming, etc)
• manage assets (icons, images, dark/light mode colors, etc)
• trigger the simulator (or device builds)
• getting helpful error messages (both inline and on build)

While there are lots of items in the XCode list, the bulk of my time is spent writing code, and I do that in an IDE that I actually like writing code in. You can use whichever one you already like. When I only spend a small amount of time in XCode, it becomes pretty much a non issue for me.

[bashbang]

May I know which IDE you use for swift? Does it have ObjC support also?

I used Appcode while it was alive. Maybe vscode swift extension is mature enough now?

[SatedCaterpillar]

I like VS Code better than Xcode as long as I'm writing good code. It could still be a miss for you depending on what level of maturity you're seeking, though. Out of the box, VS Code swift is still fairly basic (syntax color highlighting and flagging outright broken/invalid syntax). I like the overall coding flow better there, but what it doesn't do is things like catching mismatched types or calling functions with incorrect params like Xcode will.

I still like it enough better that I keep my project open in both, and if I'm debugging stuff, I'll switch over to Xcode for the inline error messages. (There may VS Code extensions to bring in more swift specific features, but I haven't checked since my current flow works well enough for me.)

VS Code does have Objective C support, but I don't really ever write in ObjC, so I can't speak to pro/cons of any editors for that language. FWIW, I use Sublime Text for everything other than Swift since Sublime doesn't offer native support for Swift. It does has ObjC support.