4 ms·
The author’s takeaway here is “If your target platform is iOS 14, you’re now good to go with hobby projects or individual screens in SwiftUI.” I think that’s g
by usmannk 6y ago
The author’s takeaway here is “If your target platform is iOS 14, you’re now good to go with hobby projects or individual screens in SwiftUI.”
I think that’s generally pretty reasonable but in my experience you won’t even be able to reach the end of your hobby app without hitting some wall where a feature you want is simple in UIKit and not supported at all yet in SwiftUI. SwiftUI is great, the paradigm is refreshing but unfortunately it just isn’t ready yet.
- jamil7 6y agoThe way I've been doing it is to mix the two frameworks together and that seems to be working out, it's easy enough to wrap UIKit views in a SwiftUI project or go the otherway and introduce some SwiftUI components to a UIKit app. I feel we won't see "complete" SwiftUI apps for another 2 years or so, maybe thats the intention?
- usmannk 6y agoYeah, that's more or less the only way to go if you want to use SwiftUI. Personally at that point I just prefer going full UIKit instead. > I feel we won't see "complete" SwiftUI apps for another 2 years or so, maybe thats the intention? Unsure about intention but it is definitely the expectation :)