.png)
.png)
Welcome to the third edition of Mobile Dev weekly, hope you are enjoying your Wednesday! It's a middle of the week, so it might be a good time for you to get a cup of coffee and enjoy reading the latest updates from the world of mobile development 🍮
In today's newsletter, we will be covering the following:
- Automatic conversion from UIKit Storyboards to SwiftUI is now possible 🚀
- Indian banking app which servers over 50 million users is built on a no-code solution 🤯
- XCode 16.0 is here 🥳
- Kotlin Multiplatform vs Compose Multiplatform after 3 iOS and Android apps we built with them 🤔
Automatic conversion from UIKit Storyboards to SwiftUI is now possible 🚀
I remember trying out SwiftUI back in 2019 and trying to tell my iOS engineering manager that we should start using SwiftUI and he always said that it's not mature enough and we won't have time to migrate all of the existing codebase to SwiftUI.
Now, there is a library which can do the heavy lifting for you!
You can simply run the command from the library: ./StoryboardToSwiftUI, and it will prompt you which XIB or storyboard file you want to move to SwiftUI, and it will automatically generate all of the SwiftUI code for you.
You can check more about the library and how it works in the link in the title!
Indian banking app which servers over 50 million users is built on a no-code solution 🤯
Axis Bank, one of the biggest banks in India, announced that their iOS and Android app is 100% powered by FlutterFlow!
While I am a still a big fan of native iOS and Android, there is certainly a space for both cross-platform and native solutions, it's all about figuring out what the business needs.
This story proves just that!
XCode 16.0 is here 🥳
After a while of working in XCode 16.0 release candidates, I have finally updated to the official XCode 16.0 version, as soon as the Apple released it.
My thoughts so far:
- Working much better than the release candidates
- The errors which were there previously, are now warnings, so you will probably be able to build your code right after you migrate to XCode 16.0, just with the bunch of warnings
- I love the feature that the images from assets will be displayed in the editor as soon as you start typing Image(.someImage)
My XCode 16.0 migration went much better than expected, and much much better than the migration from from XCode 14 to XCode 15.
Kotlin Multiplatform vs Compose Multiplatform after 3 iOS and Android apps we built with them 🤔
We have successfully built three KMP applications from our clients, and one of those apps we then migrated to CMP.
Kotlin Multiplatform is an awesome way to speed up your development speed, but keep the native iOS and Android performances with the platform specific UI, while in the Compose Multiplatform, you can even share the UI components across iOS and Android.
One of our main challenge with CMP was enabling the native iOS swipe back, to make the app look as native as it could. In the end, we had to use native iOS navigation, and just wrap the compose views in the UIHostingControllers on the iOS side, and it worked flawlessly.
I have put all of our experiences, challenges, and pros and cons together in a blog post you can find attached in the section title, enjoy!
