SwiftLee Weekly
SwiftLee Weekly #278

The end of Flutter? · Losing £25,000 · Time to drop support for older iOS versions?

Join 31,000+ Swift & iOS developers — free, every Tuesday, in 5 minutes.

No spam. One email every Tuesday. Unsubscribe in one click.

This week's blog post

Sponsored

Observability that's custom-built for mobile

Despite our best efforts, sometimes issues slip through the cracks. That's why having an amazing observability tool in your corner is important to keep your app humming. Bitdrift gives you on-demand observability that's custom-built for mobile teams: no log limits, no overage fees, and no waiting on your next app release.

Learn more

Curated from the community

Swift Evolution

Last week's Swift proposal state changes. Review-stage proposals are your chance to influence Swift's future.

What I'm working on

Case studies for Swift Concurrency & Swift 6 migration

It's been a week of fun with camera simulation and Sparkle support. Especially the latter has been challenging (as you can read in this week's article), but it does mean we're now able to offer RocketSim out of the App Store.

You might wonder—are you leaving the Mac App Store?

I'm definitely not! We just found out that many companies don't allow to install apps from the Mac App Store, if only after an exception. To get RocketSim in the hands of larger companies, we had to take this step. This already resulted in continued conversations with teams of 50+ app developers (!!). Feel free to reply to this email if you want to use RocketSim with this new distribution channel.

My second priority is finishing the core of my Swift Concurrency Course. I'm currently writing the final module on migration, but I can't just simply write those lessons. I truly want to eat my own dogfood, so I'm using the contents of the lessons to migrate several open-source projects like Diagnostics. Such migration results in unexpected challenges and real-world examples that I can use to optimize my course.

One of the challenges I faced is writing logs, lock-free, but concurrency safe, into a file. I've encountered interesting resources like NIOFileSystem and this thread on the Swift Forums. It shows that a migration to Swift Concurrency isn't only about rewriting some code—it can also mean going back to the drawing table to optimze and guard performance.

Have a great week!

Enjoying this issue?

Join 31,000+ Swift & iOS developers and get the next one in your inbox — free, every Tuesday, in 5 minutes.

No spam. One email every Tuesday. Unsubscribe in one click.