The short answer is both. To write SwiftUI apps you must also learn Swift because Swift is the programming language SwiftUI uses .
Read moreShould you use SwiftUI?
In short, SwiftUI is a wonderful and very promising framework. I think it’s the future. But, it could be another 3–5 years until it reaches the same reliability and robustness as UIKit. However, that doesn’t mean you shouldn’t use SwiftUI today .
Read moreWhat is better xib or storyboard?
If you are a single developer, it is good to use storyboard because it consumes less time . If the team consists of many developers, use xib, otherwise, it is not easy to merge the modules/tasks.
Read moreIs learning SwiftUI worth it?
So, to answer the question directly: yes should get busy learning SwiftUI because it is the future of app development on Apple’s platforms , but you still need to learn UIKit because those skills will be useful for years to come.
Read moreIs SwiftUI better than UIKit?
SwiftUI takes everything Apple learned from UIKit, and provides developers with much better features that are unavailable in UIKit . One of these features includes creating even more powerful applications while at the same time using less code than UIKit.
Read moreShould I use storyboard?
The biggest benefit of using Storyboards (especially over nibs/xibs) is that you can see how the screens in your app are related . … Another benefit to using Storyboards (over creating views programmatically) is that you get to see what your view will look like at runtime without having to run your app.
Read moreDoes SwiftUI replace storyboard?
SwiftUI is not replacing storyboards ; it may replace xib in some cases. But IMHO, SwiftUI is still far from providing the capabilities of xib. Just read in SwiftUI forum to see how developers are struggling to replicate what is easily done with xib and storyboards and autoLayout.
Read more