I learn by do.
I set up a project, and assume that it will require whatever it is I want to learn, then, I figure it out as I go.
This is what I plan to do with SwiftUI. I have taken a number of courses, and read a bunch of stuff, but these have only a transitory home in my noggin.
I won't really know it, until I have done a few projects with it.
The project that I'm currently working on, is based on "classic" UIKit. I was not confident enough in SwiftUI to do it. It's fairly ambitious, and the fact that I don't know that much about SwiftUI, was the reason I chose not to use it. I have had projects, in the past, where I banked on an unknown, or partly-known, technology, only to have it hit a block, further in.
I already know what I'll be doing for the first couple of SwiftUI projects, but it will be a while, before I get there.
I set up a project, and assume that it will require whatever it is I want to learn, then, I figure it out as I go.
This is what I plan to do with SwiftUI. I have taken a number of courses, and read a bunch of stuff, but these have only a transitory home in my noggin.
I won't really know it, until I have done a few projects with it.
The project that I'm currently working on, is based on "classic" UIKit. I was not confident enough in SwiftUI to do it. It's fairly ambitious, and the fact that I don't know that much about SwiftUI, was the reason I chose not to use it. I have had projects, in the past, where I banked on an unknown, or partly-known, technology, only to have it hit a block, further in.
I already know what I'll be doing for the first couple of SwiftUI projects, but it will be a while, before I get there.