The app is a list based app, making use of the Map API and making HTTP calls. No complex maths or graphics involved.
What do you say? If not, why not?
1–10 of 44 posts
The app is a list based app, making use of the Map API and making HTTP calls. No complex maths or graphics involved.
What do you say? If not, why not?
You'd likely pay more for them to learn Swift on the job.
When they say that, they probably just mean that their developers aren't up to speed yet on Swift, so they don't feel comfortable writing it in Swift. You'd likely pay more for them to learn Swift on the job.
As jefflinwood mentioned, most likely they don't have the developers proficient in Swift and just want to downplay it. For me this is a red flag for the company.
As BSousa mentions, xcode can be a bit flakey sometimes (syntax parser/autocomplete crashes sometimes) however it automatically restarts so it isn't really an issue.
I agree with BSousa that this FUD seems like a cultural red flag with the company.
But, 'ready for production' is a relative term that must be considered in context. Apple is encouraging developers to submit apps with Swift, so clearly they think it's 'ready for production' in some contexts.
If you're building an app for which an obscure, swift-specific bug may cause a critical security or safety issue for your customers then perhaps go with objective-c to sleep better at night. Although my impression is that Swift is stable enough even for this category of apps.
But, I'd wager that vast majority of apps out there do not fall under that category.
If you can leverage other patterns, such as FP, you might be able to achieve a big speedup in writing Swift.
It also really depends on when you want to ship: if it's a bit more long-term, Swift might be a better bet (I'm assuming that in a few years from now, almost all iOS apps will be written in Swift). If it's more important that it's ready next month, ObjC might be better, because the devs will know exactly what it takes to ship it, and will almost certainly not run into unexpected issues with the language or compiler.
That said, I'm writing my next product 100% in Swift, and we're on schedule to ship in 2 weeks. I wouldn't have done it any other way, and have seen a big increase in productivity and fun.