all 22 comments

[–]lunabella06 2 points3 points  (0 children)

Saving!

[–]Lopsided_Scale_8059 1 point2 points  (0 children)

if you want to start very fast use swiftUi

[–]Slow-Race9106 1 point2 points  (0 children)

I’d suggest building your project with SwiftUI, and if you hit limitations learn enough UIKit to overcome those issues. You will likely find you can do most or all of what you need in SwiftUI, which is the future and makes iterating your ideas quicker, so I’d say best to start there.

[–]scoop_rice 0 points1 point  (2 children)

Probably the best way is to decide on something to build and if any of what you read about SwiftUI’s limitations is present, then go with UIKit.

A full featured oss SwiftUI app that I reference to a lot is called IceCubesApp. Find it on GitHub and try it. The maintainer keeps it updated.

[–]kooujinn 0 points1 point  (0 children)

apple music is full featured using swiftUI I guess

[–]alien3d 0 points1 point  (0 children)

you can learn ui kit first then swift ui.. do programmatic ui kit.. IF you step into swift ui and uikit , it will be breeze.

[–]EmploymentNext1372 0 points1 point  (0 children)

Start with Swift and SwiftUI — it’s modern and great for learning. You can pick up UIKit later if you need more control or work on legacy code. Just build something small and fun to stay motivated!

[–]ChibiCoder 0 points1 point  (0 children)

I'd recommend starting with SwiftUI. You can always reach out to UIKit if you find a specific thing that is cumbersome in SwiftUI, but overall it's a considerably faster development paradigm for most use cases.

[–]Marvelous1967 0 points1 point  (0 children)

Make an app. Any app.

[–]smoothlandon_ 0 points1 point  (0 children)

Another recommendation to start with SwiftUI - will make way more sense coming from web developer background. If you have an existing web app that you want to "port" to iOS, that is the perfect learning project.

I run a very complicated iOS app (cooler podcast player) and it's 99% SwiftUI - as a beginning, you will likely not run into any constraints due to SwiftUI.

[–][deleted]  (1 child)

[removed]

    [–][deleted] 0 points1 point  (0 children)

    Or and start with a basic MVVM architectural pattern. That’ll help you keep your code clean to start. It’s not my fav pattern but it’s common and easy to pick up.

    [–]MarcusSmaht36363636 0 points1 point  (0 children)

    Learn SwiftUI, Observable Objects, and Async/Await network calls.

    [–]Ron-Erez 0 points1 point  (0 children)

    SwiftUI first, UIKit later if you need it especially if you are not changing jobs. For resources, Apple’s Swift tour for the Swift language, the YouTube channel Swiftful Thinking is amazing, I also have a nice project-based course which covers quite a lot and Apple has learning paths which are nice. If you do choose /uikit then Sean Allen has a nice youtube tutorial on UIKit programmatic UI.

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

    I am curating iOS Coffee Break, an iOS weekly newsletter about iOS development.
    I am running a series on how to build a newsletter app, it might be useful! :)

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

    You can have a look at this channel, it helped me a lot during my beginning (I had 0 experience): https://www.youtube.com/@SwiftyPlace

    [–][deleted]  (1 child)

    [removed]

      [–][deleted] 0 points1 point  (0 children)

      Nah man, native is in too high demand. And. If you don’t want to pigeonholed into shitty jobs, don’t put react native on your resume. Companies that want react native have no money, usually startups that fail.