Wow! Such a big recap/roundup of a promised and expected fixes!
At the moment personally for me: small utility apps with not complicated navigation (even with Deeplinks) will be a "good to go" with SUI. Firstly used NavigationStack also brings positive feelings. Multiple sheets? Still causes some trouble. LazyVStack & Grid / UICollectionView - based on sources and amount of data. Would wrap in UIViewControllerRepresentable.
Were surprised by Text performance. Will now put an item to check before publishing.
Some of the fixed items just came near by. How would we feel without Map, AttributedString or ScrollView offset? also there is an interesting thing: UIKit code-generation. Amount of trained data for UIKit is bigger than SwiftUI since it's existed longer. That's leads to variety of code styles, ideas and solutions. While SwiftUI declarative style generated easily IMHO. At least from what I personally see (don't assume that's it's a research or something). UIKit has more DSL libs also with different usage styles. How the world changed ) Now we need to keep this in mind too..
Thanks for reading. Actually I do have skipped the part how the AI tools affect how we code. I agree with you about how the AI is trained largely on the UIKit code, and it may generate much more precise or correct code: but for me, that will still be a one-time code that is hard to maintain, especially for UIKit.
So regarding code-generation, currently I would prefer to write it on my own, and accept the "tab" suggestions which I believe it's generated based on the current context.
Wow! Such a big recap/roundup of a promised and expected fixes!
At the moment personally for me: small utility apps with not complicated navigation (even with Deeplinks) will be a "good to go" with SUI. Firstly used NavigationStack also brings positive feelings. Multiple sheets? Still causes some trouble. LazyVStack & Grid / UICollectionView - based on sources and amount of data. Would wrap in UIViewControllerRepresentable.
Were surprised by Text performance. Will now put an item to check before publishing.
Some of the fixed items just came near by. How would we feel without Map, AttributedString or ScrollView offset? also there is an interesting thing: UIKit code-generation. Amount of trained data for UIKit is bigger than SwiftUI since it's existed longer. That's leads to variety of code styles, ideas and solutions. While SwiftUI declarative style generated easily IMHO. At least from what I personally see (don't assume that's it's a research or something). UIKit has more DSL libs also with different usage styles. How the world changed ) Now we need to keep this in mind too..
Thanks for reading. Actually I do have skipped the part how the AI tools affect how we code. I agree with you about how the AI is trained largely on the UIKit code, and it may generate much more precise or correct code: but for me, that will still be a one-time code that is hard to maintain, especially for UIKit.
So regarding code-generation, currently I would prefer to write it on my own, and accept the "tab" suggestions which I believe it's generated based on the current context.
Got you!