Let’s talk about our decision to migrate the preparation, development, and testing and finally, how we successfully launched it with minimal customer impact. We knew going into the migration that it wouldn’t be a trivial process, but we learned and experienced a lot of unexpected things along the way. We migrated our four-year-old Objective-C + Swift framework to pure Swift while retaining Objective-C support for our users with only the absolutely required API changes. When StoreKit2 was announced, we decided it was time to make the switch. Objective-C tooling and distribution were both stable and battle-tested, plus Jacob refused to learn Swift (and probably won’t ever have to - good job waiting that one out!).įour years later, Swift is mature and stable, and there’s a well-trodden path for distribution. At that time, Swift was still undergoing significant changes, and Swift SDK distribution was still not feasible in most cases. You can use 'Swift + Objective-C' as of now to make your app running smoothly and also giving updates regularly rather than waiting for the months to convert it completely.When we first started RevenueCat, Jacob wrote our first SDK.You may end-up having clean code under proper structure.You may find some unusual code or libraries lying around.

Andreas Oetjen Suggestion: You might start by separating the class hierarchy, and convert one 'subtree' after the other.Besides, you can also build modules from scratch in the form of smaller projects and then just drag and drop in Objective-C project.Once you are done with smaller ones, slowly start picking up big modules also you may find open source Swift libraries which are in Objective-C in your project.Reference: How can I import Swift code to Objective-C? From your project, first of all start picking up smaller modules which don't affect app in any way and see that the 'Swift' file works well with Objective-C (Your old code).Rather than start converting complete project, adapt modular way.Pick the latest version of Swift (i.e.So what I suggest you to go via following way: The biggest problem is that Swift is still evolving and probably next year we might see 'Swift 5.0'. Your approach of converting Objective-C to Swift is wrong! Apple also took time to adopt Swift completely in their frameworks and the news is in 2018, 85% of the frameworks are converted to Swift, so the point is they has also taken nearly 3 years to get it done!

Objective c to swift migration