

I look forward to talking about this with the community and hopefully getting some help with development.Īny questions, comments, or feedback in general is welcome. I’d encourage anyone interested to check out the documentation on the website. This list of features isn’t to say there aren’t any bugs, of course - I’m doing my best to keep track of them and fix them on a daily basis. If Gryphon isn’t the right fit for them, they’re left with a Kotlin codebase they can keep maintaining. You can convert the processing logic from Kotlin to Swift manually, but the UI code and anything that interacts with sensors on the device will need to be re.

Xcode integration, with Xcode showing any warnings or errors raised by the Kotlin compiler next to the Swift lines that originated them, so users can fix them at the source.There’s a templates system that’s used to automatically translate many standard library types and methods.There’s an automated test that makes Gryphon translate its own source code, with around 12k lines, and ensures the translation passes all the same tests as the original executable. The generated Kotlin code works the same as the Swift code it came from, no edits needed.This is the first version where all features are working:
