Problem with Swift 6 Concurrency, List vs. ScrollView, App Intents, LazyVGrid & More

In the July episode of Swift News I keep you up to date on the latest in greatest in the world of iOS development, Swift and SwiftUI. In this episode I discuss my experience migrating an easy codebase to the new Swift 6 Concurrency as well as the following topics:

- LazyVGrid
- SF Symbols
- App Intents
- List vs. ScrollView/LazyVStack
- App Revenue & Downloads
- iOS 18 Dark & Tinted App Icons
- App Store Screenshots
- macOS for Indie Devs
- Code is Like Art

All Links are kept here -Swift News GitHub Repo:

My iOS Dev Courses:

My Source Code:

X (Twitter):

Book and learning recommendations that help out the channel if you decide to purchase (Affiliate Links):

Mark Moeyken’s SwiftUI Books:

Paul Hudson's Hacking With Swift:

RocketSim - Enhance Your Xcode Simulator:

Timestamps:
0:00 - Swift 6 Concurrency Migration
4:57 - LazyVGrid - SwiftUI Field Guide
5:40 - SF Symbols Guide
6:32 - App Intents
8:30 - List vs. ScrollView/LazyVStack
11:00 - App Revenue & Downloads
12:11 - iOS 18 Dark & Tinted App Icons
13:10 - App Store Screenshots Are Easier
13:37 - macOS for Indie Devs
15:09 - Code is Like Art

#swift #softwaredeveloper #iosdeveloper

[zabaizabai]

Swift has turned into a gigantic, super complicated bag of special cases, special syntax, special stuff - Chris Lattner, creator of Swift

[marceljaeger]

I love this format. Every month I look forward to the next video of Swift news. Thanks for your summarising!🙏

[Kijubei]

We have a codebase that is 12 years old. One of our more experienced developers went to migrate our app to make it Swift 6 compatible. Yea, that took like 3 months and after that, we had to reverted a TON of those "fixes" because it changed or destroyed a lot of "timings" of when things got computed, passed on etc. We are pretty doomed, tbh.

My tip: Don't just try to "make the warnings / errors go away"! Think carefully about why each error appears, what it implies and what the needed fix is to ensure everything works correctly again. Only fix the easy one first and make tickets / tasks about the harder ones, they DEMAND careful consideration and reworking of components, so take your time or you will harm your code!

[KanyantaMubanga]

Fantastic as always, Sean! Thank you.

[SanusiAdewale]

I have been saying this, Swift is becoming too complicated. this wasn't how its supposed to be, its becoming the opposite of what it was set out to be.

[Ryland-tupj]

Can you make a vid specifically about how to make good and clean swift ui

[acushway]

Man that was a jam packed video. Lots of things I need to look into. I'm still not sure what I want to do as far as swift 6 goes. Frankly it scares me a bit. I have a bunch of apps on the store and many of them still have a fair bit of Obj-C. New code is all swift but I'm still way more familiar with the old concurrency than Async/Await and I've never used Actors. Starting to try and write new Screens in SwiftUI at the moment and going through Paul Hudson's 100 days course but I find that keeping up with the pace of change while working on a bunch of apps (full time indie for 12 years) is pretty hard going. Not to mention learning enough Premiere to make videos for onboarding / subscription screens... At least it isn't boring :)

[ChristopherCricketWallace]

We're being reintroduced to the idea that we need to pay for software--because it takes work to make them and keep them running, updated, and secure. It can't all be free (and that's a good thing for more than one reason)

[petersuvara]

The pertinent question is, how do we deal with the decreasing use and adoption of Swift as a developer language in general?

[dave]

Great video. I think your link to the macOS article is wrong on your GitHub. It takes me to a tweet...

SwiftUl Field Guide in HTML 🤯 keep watching.

[ChristopherCricketWallace]

Swift complexity is getting out of control. I think it's all very interesting; but the complexity is ballooning and becoming more and more opaque.

[meamanik]

All these discussions about the new feature, don’t you guys have to support old iOS versions. What do you do when the development target is ios 14/15

[zabaizabai]

I am really starting to dislike Swift. Just coding apple for fun, not really. Good for content creators, sure.

I knew "networkquality -c" that I would use :) I can't change like this yet but it will come Swift 6 and on, there is no materials wich Tables stuff.