Definitely the Power Pack, but save your money and follow my free 100 Days of SwiftUI first: hackingwithswift.com/100/swiftui

with the advent of the Corona virus traditional schooling will die (at least that's my hope)

Ali Aljoubory you need the Xcode beta, which runs on Catalina beta, and you can only target iOS 13 or higher. I’m not sure wether Swift 5 is required but it’s set by default for new projects.

It’s required xcode 11, swift 5.1 and iOS 13 to run. I think it’s too early to make production apps with swift ui, because there will be still users with iOS 12 in next 1-2 years

Yeah but where is today Objective C ? So that far will go UIKit to will disappear as well just like Objective C so UI Swift will be taking he's place very Soon

@@raitasorin Not that soon, i suspect that another 2 solid years uikit will still be top. Then slowly fade away. The swiftui will need at least 2-3 years to mature at the point where you can make a real complex app. UIKIT is here for 10 years now...

Guitaripod not my iPhone 6...

staybalanced it’s time to move on from 2013 my friend

Guitaripod give me one good reason of a feature to upgrade. I haven’t been moved to get a new phone new features seem more like gimmicks

@@dwayneneckles You already answered your own question 😸

​@@guitaripod iOS 13 still has quite a few awful glitches. Forcing people to dispose a working device for sake of new way of arranging views in the editor is kind of a weak excuse. It's not revolutionary either. React Native goes with this concept a bit better: more forgiving view state management, stylesheets, etc. I have new devices for testing, but iPhone 6 is still more usable, even after I bought lightning-audio-data port adapter. TBH, newer iPads have sidecar option and apple pencil. First one is slightly glitchy, but second one is a killer option (both in terms of usability and price)

I imagine to do it properly with display scaling

I meant to say prior to SwiftUI not prior to UIKit

@@Heraclix It's NOT "always more clear to have everything in code"… that's purely your opinion .

I think you’d be surprised at the percentage of UI in the top chart apps that is not storyboard based. There are trade offs between code and storyboards, and the larger the team and longer lived the app, the worse storyboards look. That’s a big part of why swiftui is so exciting, we can finally use interface builder without most of the downsides.

SwiftUI is still the new kid on the block, but when a UI component is missing one can always use the UIKIt version of it with UIViewControllerRepresentable

I think that'll depend on how fast SwiftUI will adopt.

i just found out from your others video, that we can use @State for this case. Can’t wait to try it out

of course.

Yes and that's why I think it's not really a fair comparison. UIKit is meant to be "meant to be" used with the storyboard to set stuff up and then programmatically tweak it a bit. I think it would have finished very close if not faster.

@@punishedbrains9954 Using SwiftUI ist much faster then Storyboards and UIkit. Example: Try setting up a table with Storyboard. You will have to add it to Storyboard, add a cell, design the cell. Then drag everything into your view controller. Then add the delegates, and delegate methods, then implement the code to tell the table how to deal with the data, which you will also have to implement. Now compare all this with how it works in SwiftUI: Just wrap whatever content you would like to have in a cell in "List(){..}". Finish. ^^Thats it. No Protocols, methods, data, etc.

@@Seitenwerk except when your table starts to grow immensely. Or if you'll need to perform animated edits to the table. Or if you need just to scroll somewhere in the list. Or basically anything other than a flashy demo. I think SwiftUI has giant potential but it's still just a tool for quick prototyping

@@Seitenwerk Really? With a simple right click you assign the delegates. And the methods of the tables I have them in a snippet

Also using layout frameworks for doing layout is much faster way to go

Jeffrey Haines after five months of using SwiftUI I'm regretting my original comment 😂 SwiftUI is way better

Depends on what you want to do. SwiftUI is amazingly fast and easy to use, but it is definitely missing some features. For instance, if you want to do something like, say, move a textbox up above the keyboard when typing, that isn't something you can do with SwiftUI yet. SwiftUI also doesn't support a lot of elements like WebViews. Additionally, SwiftUI only supports iOS 13, so if you're planning on actually distributing an app, it shouldn't be used as a complete replacement for UIKit yet. Therefore, I'd recommend learning UIKit (at least the basics) as well as SwiftUI, since the two are interoperable. That way, you can create most of the stuff you need in SwiftUI which makes things a lot easier, and if you want any of those advanced features only in UIKit, you can embed them into SwiftUI (and vice versa).

Also, one could use awesome github repos like TinyConstraints in making layout super fast. The main difference between SwiftUI and UIKit is not how fast you can build apps, but how to approach building apps. This has also been said by Paul in numerous other videos of his.