\n<\/p>\n
How did we reach Issue 700 of this newsletter? \ud83d\ude31 For almost 14 years, writing a few words, gathering news, and promoting community blog posts has been part of my life. It makes me very happy that you still want to read it. Thank you, whether you\u2019ve been here since the first issue or joined more recently.<\/p>\n
Yet I feel a little weary as I sit down to write this opening comment. Part of it is caused by doing this for almost 14 years, and I can certainly see an end to this newsletter in a way that would have been difficult to imagine a few years ago. But the other part is specific to this week, because this week\u2019s big news in the community is around a controversy I dislike talking publicly about.<\/p>\n
Driven by Apple\u2019s return to advertising on Twitter\/X<\/a>, Matt Massicotte<\/a> wrote a blog post, \u201cLeverage<\/a>\u201d, where he tries to find something to use as leverage to protest against their use of the platform:<\/p>\n Apple relies heavily on feedback from third-party developers to find bugs in new APIs and OSes. Because of their development cycle, this is especially<\/strong> critical during a beta period.<\/p>\n So I\u2019m just no longer going to use Feedback Assistant. I will not use beta OSes. I will not share crash reports for Apple software. Because of Swift\u2019s continued use of X, I will no longer participate in the Swift forums or evolution process. I will also actively discourage others from doing these things.<\/p>\n<\/blockquote>\n He received plenty of support in reply to his announcement<\/a>, and there are more blog posts around the community supporting and discussing it. Unfortunately, petitions and protests are rarely good catalysts for direct change within large publicly traded corporations.<\/p>\n But then I read Christian Tietze\u2019s post<\/a>:<\/p>\n So why bother?<\/p>\n Because bothering is all we have.<\/p>\n Because acting in accordance with one\u2019s values on all<\/em> personal fronts is the only way to actually manifest any<\/em> pressure and change. This includes protests and boycotts and writing open letters. It also includes going to demonstrations, writing to elected officials, all of that. The task for you and me is not to \u201cchange policies\u201d, because we can\u2019t, but to make ourselves heard so that those who can, will.<\/p>\n<\/blockquote>\n My instinct with controversies like this is always to stay quiet and not express a strong opinion. It\u2019s cowardly, I know. But I admire everyone who is making this stand for trying to do something<\/em>.<\/p>\n Dave Verwer<\/p>\n Make sense of iOS user activity with OpenTelemetry<\/a><\/p>\n OpenTelemetry helps you standardize the telemetry that\u2019s collected and transmitted across different app boundaries, without needing to customize the format of the information being transmitted each time. Learn how to use the OTel-Swift SDK to trace app activity from disparate parts of an iOS codebase. Check out the guide from Embrace<\/a>.<\/p>\n Martin Pilkington<\/a><\/p>\n I was devastated to hear that Martin Pilkington passed away last week<\/a>. He was more than just a member of this community to me; I was lucky enough to call him a friend, and I\u2019ll miss him terribly. Whether it was discussing the latest Swift language updates, chatting on a call, or playing D&D or another game with friends, he was always generous, warm-hearted, and had nothing but kind words. He will be missed by many, but very much by me. \u2764\ufe0f<\/p>\n Dark mode for iOS Dev Weekly<\/a><\/p>\n There\u2019s also some \u201cnewsletter news\u201d this week, especially if you like dark mode. As you will have noticed if you\u2019re reading on the web, the iOS Dev Weekly website now supports a dark theme. If you\u2019re reading in an email client, I also tweaked the email template to look better in email clients that force a dark mode. Unfortunately, making a true dark mode email is looking like it\u2019s beyond my abilities, but hopefully the web version should give you what you need.<\/p>\n Next up is bringing back the full text RSS feed. I know people miss it, and it\u2019s next on my list!<\/p>\n Pallet<\/a><\/p>\n Pedro Almeida<\/a> with a new and free utility app for manipulating Improving the approachability of Swift data-race safety<\/a><\/p>\n I don\u2019t usually write about features that are not in shipping or beta versions of Swift, but I want to mention Holly Borla<\/a>\u2019s recent post where she details three upcoming\/proposed improvements to Swift 6 language mode. If you stuck with Swift 5 language mode so far, this should be a nice confirmation that you made a good choice. Waiting for these improvements, and potentially more like them, will pay dividends.<\/p>\n SharingGRDB: A SwiftData Alternative<\/a><\/p>\n This is interesting. Brandon Williams<\/a> and Stephen Celis<\/a> with a new library, which is an integration of their Sharing<\/a> library and Gwendal Rou\u00e9<\/a>\u2019s GRDB.swift<\/a> SQLite library. It works great with SwiftUI and they propose it as a potential replacement for SwiftData with access to SQLite features and SQL queries directly.<\/p>\n It\u2019s worth noting that Gwendal also created GRDBQuery<\/a>, which also provides an interface from SwiftUI to GRDB.<\/p>\n The Mac Menubar and SwiftUI<\/a><\/p>\n I\u2019m a big fan of SwiftUI Fundamentals: a deeper look into the framework<\/a><\/p>\n When writing about the internals of SwiftUI, it helps to be able to say \u201cHaving contributed to SwiftUI\u2019s development as part of the team at Apple\u201d, and that\u2019s exactly what Natalia Panferova<\/a> can say. She\u2019s written a new book that is both a guide on how to build apps with SwiftUI, but that also includes a look under the hood.<\/p>\n For full disclosure, Natalia sent me a review copy of this book.<\/p>\n iOS framework developer @ Nutrient (formerly PSPDFKit)<\/a> \u2013 Design APIs that will affect hundreds of apps, and create UIs used by millions of users. Collaborate globally in a small team working on the leading document SDK for iOS, macOS and visionOS. Make the most of a flexible schedule, and attend annual retreats at exciting places around the world. \u2013 Remote (Anywhere)<\/em><\/p>\n iOS Engineer @ Bevel<\/a> \u2013 We\u2019re building at the forefront of consumer health. We are a small team that deeply cares about our craft. You\u2019ll get a chance to work on something that improves the health of tens of thousands of people! \u2013 On-site (United States in NY)<\/em><\/p>\n\n
\n
News<\/h2>\n
Package.swift<\/code> files, and it\u2019s a great reminder that Xcode has no built-in GUI for this at all. There\u2019s adequate warning before saving, but be aware that it completely<\/em> overwrites your Package.swift<\/code> with its own version when you save.<\/p>\nCode<\/h2>\n
NotificationCentre<\/code> so I was happy to see Sarah Reichelt<\/a> use it to hook up menu items in a Mac app. There are great tips for using notifications better in general in the post, so it\u2019s worth a read even if you\u2019re not hooking up menu items.<\/p>\nBooks<\/h2>\n
Jobs<\/h2>\n