Suggested approach: Try to be thoughtful here – coming down hard on one side rather than the other isn’t a good look, so instead try to think about what each framework does well and less well.
For example, UIKit gives us endless customizability, for example, as well as access to almost the full range of iOS UI tools, but takes a lot more code to use and you need to handle all the state changes properly. On the other hand, SwiftUI gives us access to fewer iOS components, but takes less than a fifth of the amount of code to write and does a huge amount of extra work for us.
Estimated difficulty: Easy
Link copied to your pasteboard.