Migrating Existing Projects
Unfortunately, there's no reasonable way to improve the Kotlin-Swift interop without causing some source-breaking changes. Therefore, you will need to migrate some of your existing Swift code after adding SKIE to your project.
Existing Kotlin code shouldn't need to be changed. SKIE is designed to compile any Kotlin code that can be compiled with the official Kotlin compiler.
We've put a lot of effort into making the migration process as user-friendly as possible. For example, SKIE is fully configurable; therefore, you can selectively enable/disable specific features in specific parts of your code. Thanks to that, you can do the migration iteratively and whenever you want.
But before you start with the migration, you should first read the SKIE features documentation, including the detailed docs for each feature you want to use. This will give you a good idea of what you can expect from SKIE and what changes you need to make to your Swift code.
The next step will depend on many factors, like the size of your project, its complexity, the number of developers working on it, and what SKIE features you want to use.
Small, simple projects can probably get away with installing SKIE without much further preparation because you will likely get only a few compilation errors that can be quickly fixed.
On the other hand, migrating large projects with many developers on board tends to require more work. In those situations, we recommend preparing a migration plan, and you should also make sure that all developers are familiar with SKIE.
Touchlab offers additional content and consulting services to make the migration process easier.
You should definitely check out the SKIE Migration Guide, which will help you create your customized migration plan.
If you want a more personalized approach, we can help you migrate your project.
Once you are ready to start the migration process, go to the installation documentation and add SKIE to your project.