Member Avatar for pro-tek

IS IT BETTER TO MOVE TO SWIFT OR STAY WITH OBJECTIVE-C?

Edited by pritaeas because: Moved to software dev.
  • 3 Contributors
  • 2 Replies
  • 285 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by JamesCherrill

Dani AI

Generated

Both and the responders lean toward moving on, but the short thread misses a practical, low-risk migration path. The choice should match the codebase, release cadence and team skills rather than be purely trend-driven. A balanced strategy gives modern language benefits while keeping existing apps stable.

A pragmatic plan:

  • Inventory and test: add or expand unit tests around modules planned for change; tests are the safety net during rewrites.
  • New work in the newer language: implement new features and screens in Swift; keep well-tested legacy components in Objective-C until converted.
  • Migrate small modules first: pick a contained, high-value module with good tests and convert it end-to-end to validate process and measure risk.
  • Interop rules: expose only minimal Objective-C APIs to Swift via a bridging header; prefer thin, Swift-friendly wrappers over large, direct conversions.
  • Tooling and CI: lock a Swift toolchain, enable continuous integration and automatic Swift-version migrations from Xcode when necessary.
  • Third-party checks: confirm pod/Carthage/SwiftPM support before converting code that depends on external libraries.

Common pitfalls and cautions:

  • Pay attention to nullability annotations, optionals and API naming — they change how code is written and tested.
  • Watch for subtle differences in value vs reference types and thread safety when moving logic to structs or enums.
  • Keep ABI and toolchain compatibility in mind for binary frameworks; plan releases so library updates align with migrations.
  • Maintain Objective-C familiarity on the team for debugging, profiling and crash analysis during the transition.

Conclusion: adopt the newer language for new work and incremental rewrites, but keep Objective-C competence for maintenance. A staged, test-driven migration minimizes disruption while letting the team gain the newer language benefits on a controlled timeline.

Recommended Answers

All 2 Replies

Member Avatar for hericles

I haven't moved onto Swift myself yet, mainly because I've been doing less native coding and doing more cross-platform stuff, but from what I've read Swift is getting being picked up at a high rate due to it's ease of use and coding style. Google are even thinking of using it as the OS for android in the future. (Apple have made Swift open source apparently - who would have thunk it).
It's based on Objective C so the learning curve for you shouldn't be very steep. I say switch.

Member Avatar for JamesCherrill

When Apple adopt new technologies they usually do it hard and fast. Don't be surprised to see new hardware or software features getting support in Swift first, then before too long, in Swift only.
I say switch too.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.