Let me run a scenario by you. You’re just back from vacation in the Maldives, and your friends are very curious to see photos from your fantastic trip. You unlock your phone, open your photo album and make sure that there’s nothing private hidden in between those beautiful (albeit predictable) beach and sunset photos.

Learning tweak development has been a very giving and exciting experience. I’ve not only been able to create tools which would have never been possible on non-jailbroken devices, but also had the possibility to tweak 3rd party apps, as well as testing vulnerabilities on projects I’ve been involved in. But since more and more projects are moving over to Swift, tweak development is becoming harder to do (for now). This was something that became painfully obvious after Swift 4, where the compiler became much more conservative in making Swift methods accessible in Objective-C; something that certainly wasn’t the case in previous Swift versions.

At the end of last week, I updated two of my existing apps on the App Store to support changing languages within the apps themselves. While I already have this functionality in two of my other apps, the apps I just added this to has a much solid use case, and is arguably something I should have done a long time ago.