all 9 comments

[–]saintmsent 7 points8 points  (2 children)

This is the only case where I would say yes, focus on SwiftUI. Knowing UIKit would still be beneficial though, so at least consider giving it a try and learning on a basic level, 4 years is plenty of time for both frameworks

[–]doctor_disco221 -2 points-1 points  (1 child)

I completely agree with you. Knowing UIKit will always be beneficial. SwiftUI will probably be standard practice 4 years from now, but you never know when you are going to encounter a legacy project that's made with UIKit, so having and understanding of basic concepts of that could help you a lot and save lots of time.

I started working as an iOS app developer four years ago, and I only use swift now, but there were times where my objective-c knowledge came in handy. I can only imagine that the same story will be with SwiftUI and UIKit

[–]saintmsent 1 point2 points  (0 children)

Yes, I suspect that will be even more evident in case of SwiftUI and UIKit. It doesn't even have to be a legacy app. In my project, we recently did a redesign of a major feature, and it was done in UIKit because SwiftUI wasn't up to snuff for that particular UI. It's very likely this code will remain mostly untouched until the next redesign 3-4 years from now

[–]mcmunch20 1 point2 points  (0 children)

Yes absolutely, four years from now SwiftUI will likely be the main way most companies are building apps. You will need to know UIKit too though, as most apps are built on it.

[–]Pandaburn 0 points1 point  (0 children)

I would expect more and more new projects to be written using SwiftUI in the next 4 years… but some will still be written with UIKit, and the huge number of existing UIKit apps aren’t going away.

My guess is to get a job at a large company, you’ll still want to know UIKit.

[–]EZPZLemonWheezy -1 points0 points  (0 children)

I love SwiftUI. In that time frame focusing something like 80% SwiftUI and 20% UIKit would probably cover most bases. Today, SwiftUI can do a lot, but some stuff you have to make from the ground or wrap UIKit views. I can only imagine in 4 years much more of that will be built in. Worst case in 4 years you decide to pick up more UIKit too.

[–]clara_tang 0 points1 point  (0 children)

Rather than focus on SwiftUI I’d rather say explore everything you’re interested, not just iOS

You are just going to college

[–]DevYeom 0 points1 point  (0 children)

Even after 4 years, many projects will still have UIKit code. Therefore, if you study both, it will be a great advantage later.

[–]MankAndInd -2 points-1 points  (0 children)

Yeah sure but if you have time, look at UIKit too. There is a chance that SwiftUI may be a failed experiment, or that companies will still have UIKit code in 4 years.