SwiftUI vs UIKit – Comparison of building the same app in each framework

Why didn't you use a storyboard on your StarshipViewController and just pass around the values? Although sometimes buggy, I think the storyboarding is one of the strengths of UIKit

Paul is your opinion about UIKit is still relevant by 2023?

sorry what is the point of your video? fast forward wanking about your code?

This video is ridiculous... it doesn't compare the speed of both languages... it just SHOWS YOUR OWN LIMITED knowledge on the given languages... A fair competition would be 2 different people, highly skilled and advocates of each clashing in multiple different small chanllenges

I love your videos... I know I'm late to respond but to be honest, I would rather like to see a video comparing the headaches involved in trying to figure something out that is not working as expected and the time it takes googling or jumping into the documentation for solutions. I think in that case, SwiftUI development might be slower (but that's just me).

the course I bought is ios app development - angela yu from udemy and it is based on xcode 12 (when ui kit was still used) but this is 2023 and xcode is ont having uikit option we create a file based on swift ui, what should I do ??? please help

Great! Thank you very much 🙂

Hi, thanks a lot. What is yours opinion about start learning SwiftUI in 2023? Or you strongly recommend to learn UIKit as well?

Mate, this is funnier than expected! You make UIKit look like an old timer :) This video definitely convinced me to move into SwiftUI prototyping as honestly I've got completely cluttered into Storyboards and ViewControllers mixed with code and seques and all of that ... just to build the prototype for development... :)

you are code gun!

What is LOC?

I have a question. Do you Australians really catch and eat a crocodile every Saturday?

Thanks.
What about memory footprint and performance?

Thanks Paul for this great video! I actually started to use SwiftUI on my main project couple of months ago and I'm mostly satisfied except for one problem which is backward compatibility. Many great features of SwiftUI today are exclusively available for iOS 15 which makes me feel that I should've waited for a year or two not to get new features but to only use the existing ones while being able to support at least two major versions of iOS

Thanks you for your videos to help us to learn swift. Have nice Christmas.

Lewis Hamilton
Is the GOAT in F1

Thanks Paul, very informative. I'm starting out with IOS development and I needed to know what I am getting myself into. You simply made things easier for me. I truly appreciate you.

This is a great video comparing the two platforms, amazing... thanks for this...

Side by side comparison is a really cool idea! Thank you for you work, Paul 🙏 You are amazing!

Thats not even fair comparison who codes UIKit with this verbosity? - you do this things in interface builder with auto layout and stuff

I wonder if UIKit would be quicker if you use storyboard to define the layout rather than doing it programmatically?

Thanks for a great video! I'm curious, which you did first - UIKit or SwiftUI version?

I'm not sure how valid this is, usually you use SnapKit or some extensions for constraints, but also you choose app format where SwiftUI really shines. Anyway nice comparison, thank you.

what was the real time without speedup? only detail I am missing, nice work overall!

I did the math and, comparing the difference in time for a simple app like this you would save around 36 hours of coding.
This only applies if you know what you're doing without googling anything, this what makes a difference I guess because UIKit has a larger community now than SwiftUI.

Excellent video. Thanks! Just subbed.

The even excellent excited wilderness intradurally ruin because permission corroboratively empty modulo a unhealthy brian. berserk, aboriginal vase

I like the simplicity of SwiftUI but it’s still a very buggy framework as far as I observed within one week of using it

Compatibility.
Unfortunately SwiftUI is only available for iOS 13.0 and higher.

Using SwiftUI would thus mean that you can no longer support people with older devices.
There are still millions of iOS devices out there with iOS versions older than iOS 13, and are no longer be updated because Apple (policy) does not supply updates for this older devices.

Take, for example, a banking application with millions of users. Of course, as a bank, you must support as many devices as possible, even those that are bought a long time ago. These are your customers, were you are depending on, whether rich or living on a small budget.

Note that for a lot of people, iPads and iPhones are relatively expensive devices. if you live on a small pension budget, in many cases you can't even afford to replace your iPad or iPhone There are millions out there that can't.

That is why I make my apps available starting with iOS 9. Unless special features only available in later iOS versions are needed e.g. like AR. I have absolutely no problem with targeting starting with an old iOS version. (but maybe Apple has, because from a commercial point of view of a hardware seller, it is more profitable to "encourage" people to replace their devices as soon as possible. However, I wouldn't go that far to say that Apple is introducing new tools like SwiftUI all the time for that very reason..)

Using UIKit is not so hard as it might look for beginners, especially when using a language like Swift.
Paul, you're talking about a lot of boilerplate code, and yes, using UIKit needs more of that, but most of it in my apps is written-once-use-anywhere in class extensions or even UIKit sub-classes that I've made.
(the latter is one of the advantages of using Object Oriented programming, you haven't got this flexibility with SwiftUI because it is based on structs instead of classes) So, in the end because of extensions and sub-classes, my apps are relatively small and run great even on the older devices. No problem.

In summary, in this perspective, to get a job as iOS developer, it is very important to master UIKit because at many companies, SwiftUI cannot be deployed, simply because it is not available in older iOS devices that need to be supported.

There is a social aspect to this too, think about it, e.g. maybe you have (grand)parents who are happy with their older iPads and iPhones. so restricting or upgrading your apps to a higher iOS version counts them out.

Not fair at all, there is no need to create detail view controller in code, you can just drag and drop UI controls on storyboard and create whole screen easy. This would for sure reduce lines of code for UIKit, and I think you did it on purpose this way. I don't say UIKit is better, or that SwiftUI is better, just that this was not good enough comparison.

I’ll be doing your 100 days of SwiftUI soon.

Thank you!!

This is amazing on so many levels. Having bumped into your channel has been a great thing.
Thanks lot for these.
Had a question, was checking your Gumroad and for a complete beginner on Swift (but not so much on programming, I mostly do C# and shaders) which pack should I begging with? Power Pack or Plus Pack?
Cheers.

The layout part that wasted most of the time for the UIKit version was done wrong, you don't need to use stacks, in fact stacks makes it harder. You can do it very quickly in many ways, I can do the entire constraints of that view with just 5 lines of code using constraintsWithVisualFormat.
Anyway, "faster" or "less code" is not a suitable measure of how good something is. When it comes to code, you might have to spend more time at some point, but it saves you time later.

So the moral of the story is use UIKit and charge by the hour.

I am new to swift and this is great advice. Never knew what they were until now

I'm pretty sure this was faster constructed in Interface Builder. Having both projects finished around 9 minutes.

been here for decades??

That was Great Toturial easy comparison.

Really inspiration video for me. As react native developer,I don't know about it much. I want to know the SwfitKit and UIKit. Your video made me clear. Thank you.

Gratitude...Gratitude... Gratitude... All Best in your own Great Way

I think you should make the second vc in storyboard and then compare.

Great video, although i feel it was not very fair to UIKit. It has storyboards and it is a greate advantage, if we had done all the code in storyboard - it would have taken equal time to SwiftU, and code lines would have been shorter. I love storyboards and do not code programmatically much, so maybe i am biased. But storyboards make creating UI super fast, in fact at first i found it faster than SwiftUI.

Question: If I'm jumping into iOS programming, and I am using the Stanford 2020 SwiftUI class (on the multithreading lecture now) ... am I doing well, or should I have backed up and learned UIKit / Storyboarding first ? Curious as to your opinion

True but not sure it will be the same while handling datas manipulation and complex actions. SwiftUI is great to design screen but when you try to manipulate datas its need a lot of thinking.

What about next 4 years time? Will Swift ui be the norm in 4 years?

thanks!

Damn it. It took me a month.

Please do help me sir

Sir how can i pick videos like in image picker SwiftUI