I remember when swift charts launch, a friend of mine was in tears because it launched 3 days after he painfully completed a UIKit project which had charts in it , getting its data from a raspberry 😂😂
People who don’t have a lot of multi threading experience may not realize just dumping everything on a mainactor thread has large implications for latency and responsiveness. It’s easy to block threads by accident. I’m curious how all this will work out.
are there resources to learn more about multi threading and performance? I was shocked when I realised a side project was using 468MB of RAM, all it did was get data from an api and display it
@@SanusiAdewalelet me know if you find anything too :( all I know is that UI changes go on the main thread and everything else doesn’t get priority as far as I know
@@riken2567 I think the general recommendation is, if you want a job *today*, then learn UIKit, but if you want to build your own apps from scratch, then SwiftUI is the way to go. SwiftUI will also help you build for all platforms from watchOS, iOS, visionOS to macOS.
Learn more with my iOS Dev courses at seanallen.teachable.com
I remember when swift charts launch, a friend of mine was in tears because it launched 3 days after he painfully completed a UIKit project which had charts in it , getting its data from a raspberry 😂😂
Bummer for your friend, but Swift charts is amazing!
What I really want is for Xcode to be able to also build Android and Windows apps from Swift/SwiftUI source.
SF SYMBOLS are my favorite thing too! 😄
Thank you Sean!
No problem, Dave :)
People who don’t have a lot of multi threading experience may not realize just dumping everything on a mainactor thread has large implications for latency and responsiveness. It’s easy to block threads by accident. I’m curious how all this will work out.
are there resources to learn more about multi threading and performance? I was shocked when I realised a side project was using 468MB of RAM, all it did was get data from an api and display it
I think the expectation is that anything not part of the UI should be done on another thread
@@SanusiAdewalelet me know if you find anything too :( all I know is that UI changes go on the main thread and everything else doesn’t get priority as far as I know
@@aronianspigonian8589 I will
🔥🔥🔥
Has anyone seen how to do the dark mode icons? I haven’t had any luck making that work
It’s currently in Develop beta(only works with Apple’s own apps rn) , will be in the upcoming public beta, official release in September presumably
Keep it up 🎉
Will do
Thanks Sean 👏
No worries
still no new objective-c version... :(
Sadly… objc still be something different that make me feel like I’m getting more power
"Apple Intelligence" is eerily Orwellian
1st
it's 2024 should i go for Uikit or swiftui
If you want to be able to work on legacy codebases, learn both. There are still a lot of apps that have not been ported to SwiftUI
@@Twimmy15 thanks brother can you guide me more
@@riken2567 I think the general recommendation is, if you want a job *today*, then learn UIKit, but if you want to build your own apps from scratch, then SwiftUI is the way to go. SwiftUI will also help you build for all platforms from watchOS, iOS, visionOS to macOS.
swiftui for your projects. If you need a job in the industry then you need both to pass interviews. 4 out of 5 job adverts are requiring UIKit