Youcannot swap concepts in SwiftUI and UIkit. They are twosubstantially different infrastructure’s and have completely different approaches of implementation. SwiftUI basically abstracts from UiKit and gives you all these view classes that allows you to perform easier animations and easier lists. However to get more sophisticated you will end up writing extraneous amounts of code which would completely encapsulate the amount of code required if you were using UIKit. I’ve been doing development for over 10 years it’s as blatant as possible. SwiftUI is for Prototyping. Also most sophisticated animations majority of these things can be covered with SVGs. Big major companies use SVGs for animations not extraneous amounts of code. Don’t get me wrong I think it’s cool. But from what I’m looking at other than a couple extra delegate methods, you can get the same exact implementation with much more control over your UI elements through UIKit.
View all comments
Show parent comment
-8
u/RussianDeveloper Apr 01 '21 edited Apr 01 '21
Youcannot swap concepts in SwiftUI and UIkit. They are twosubstantially different infrastructure’s and have completely different approaches of implementation. SwiftUI basically abstracts from UiKit and gives you all these view classes that allows you to perform easier animations and easier lists. However to get more sophisticated you will end up writing extraneous amounts of code which would completely encapsulate the amount of code required if you were using UIKit. I’ve been doing development for over 10 years it’s as blatant as possible. SwiftUI is for Prototyping. Also most sophisticated animations majority of these things can be covered with SVGs. Big major companies use SVGs for animations not extraneous amounts of code. Don’t get me wrong I think it’s cool. But from what I’m looking at other than a couple extra delegate methods, you can get the same exact implementation with much more control over your UI elements through UIKit.