OK, so this is a big one. I was able to port my iOS app in Swift to Android (Kotlin) using Cursor. It was all very neat, quick and automated. At first I went on and just tried to Chat to get the changes and tweaks and lines of code I had to create in the Android project... But that approach was getting cumbersome - And here comes the actual thing. The real thing. We have to have a folder that contains both the Swift project and the Kotlin project. At first I was having them in separate places. But then just for the purpose of porting I created a folder containing both (copied) projects. To know you're copying them right (at the right folder structure level) here an example - or what to look: Users/username/porting-my-app Users/username/porting-my-app/my-app-ios (you will see the .xcodeproj file here along a Tests, UITests folders) Users/username/porting-my-app/my-app-android (you will see build.gradle.kts, settings.gradle.kts, along with the gradle, the app folders...) The basic idea is to have just one folder in Cursor that contains both versions: iOS and Android. So that Cursor can analyze the codebase and generate the appropriate files for porting. Uh, and in case Cursor doesn't detect both thingies just know you can use the @Codebase command.