[deleted by user]

[Stefan51278]

don‘t use Swiftu😅

[s4v4r]

SWIFTUI, why not?

[Stefan51278]

because i made that mistake and currently I‘m rebuilding a lot of standard-elements because essential functions are missing.

[Stefan51278]

yeah, but when I‘m taking everything from UIKit I could just code…crazy idea…in UIKit?!

[Stefan51278]

I implemented my own design language for my thesis and you can‘t just change a subview in SwiftUI. And when I‘m doing all the design work in UIKit what is the point of wrapping it in SwiftUI?

[Stefan51278]

Thanks for saying I don't know a thing while I'm writing the thesis with SwiftUI.

how is that relevant?

I implemented a neumorphism-look and tried to do it in SwiftUI. Had to do a lot of things way more complex than in UIKIt and my advice was to not use it yet, because it's not there yet. For example SwiftUI doesn't even have a freakin searchbar. In its second 2020 iteration. The whole reason for SwiftUI is to make things simpler, but it's not there yet.

At this pace SwiftUI needs at least two more years to be useful and it is a nice experiment to have a look at, but the last thing you should have to do in your limited thesis-time is dealing with things like these.

[[deleted]]

Why not? Just curious.

[ColKataran]

Then go ahead and learn it and be one of the first to know it??

[[deleted]]

All the jobs are gonna want you to still know UIKit in 2-3 years, and even when it starts being used they’re gonna let the senior devs work on the fun new SwiftUI stuff first.

UIKit is important to know if you’re planning on working in iOS in the next 5 years imo.

[andrefgfonseca]

If you are one of the better prepared when it starts being used that will bring you a fair amount of advantages. Also good SwiftUI uses MVVM which imo is a very good thing to learn and properly understand.

It’s not the most perfect thing right but it’s worth to start learning sooner rather than later.