4 ms·
Thanks so much! Yeah it's not much yet hopefully it continues to trends upwards. There's still lots of improvements to be made to SwiftUI, and a lot of it still
by rlindsey123 6y ago
Thanks so much! Yeah it's not much yet hopefully it continues to trends upwards.
There's still lots of improvements to be made to SwiftUI, and a lot of it still requires using UIKit. So it's definitely still early, but even with a lot of the quirks I still find the coding time a lot quicker than just plain Swift. I'd say it's a good time to start getting to grips with it, where it truly excels right now is in reusable views.
In terms of developer experience, there's a lot of work needed to be done to build out the amount of API's; you'd be amazed at how hard sometimes the most simeple task can be. Second part would be Xcode errors. They suck and make debugging an absolute pain. A lot of the time the error is vague or even missing the problem.
Lastly, backwards compatability is an issue. Some of the fixes they are making for it are only available on iOS 14> such as StateObject, so things like that make it annoying.
All in all though, I'm still a fan and slowly beginning to move to SwiftUI!