\n<\/p>\n
The tools and setup I have for writing and distributing this newsletter have changed very infrequently over the 13 years and almost 700 issues since I started publishing it. I started in 2011 with some Markdown files, a Mailchimp account, and Jekyll<\/a>. Then, in 2013\/2014, I decided I needed something more sophisticated. With a small team, I built a publishing tool that enabled me to construct issues via the web, host the site, and send the emails. That project went so well that it even ended up turning into a product: Curated<\/a>.<\/p>\n I ended up selling Curated to another company, and it\u2019s been sold a couple more times over the years. I was still a happy customer until recently, but that all changed at the end of last year<\/a>. Even though they did eventually get the system working again, my confidence in their ability to run the site has gone and I needed to leave Curated behind.<\/p>\n So while I was originally planning a restful break over the holidays, instead I spent most of it at my desk trying to get this complete re-build of the site and publishing platform finished. It has been an enormous<\/em> amount of work, but I\u2019m pretty happy with how it turned out. I also took the opportunity to tweak the design and to make some other small changes. You can still see the old design<\/a> for a little while if you\u2019d like to compare the two. One change that some of you will be pleased to see is that there are no more Most importantly, this rebuild puts me back in control of this website. If I\u2019d like to try some new things, that\u2019s much easier now that I control the entire rendering of the site and email.<\/p>\n That said, there are still some rough edges and things I didn\u2019t get to before shipping the site. The most important, and I know I\u2019ll get plenty of email if I don\u2019t mention it, is that there\u2019s no full-text RSS feed yet. This is not intentional, but I hit an issue with creating it that I couldn\u2019t easily fix. I\u2019m also aware there\u2019s no plain text version of the email right now, but I\u2019m not sure that\u2019s something anyone cares about? Let me know if you do.<\/p>\n My todo list also includes better mobile device support, dark mode support for both the website and email, and tidying up some other loose ends. I\u2019ll make those changes over the next few weeks, but if you see anything wrong with today\u2019s email or the website<\/a>, please let me know so I can get it fixed!<\/p>\n PSPDFKit is now Nutrient<\/a><\/p>\n New name, same trusted SDK with a slick UI and dozens of out-of-the-box features for document viewing and editing. Powering hundreds of popular iOS apps like Dropbox, Box, and Autodesk, as well as our own PDF Viewer. Check out our blog<\/a> to learn more about what we\u2019re doing \u2014 from designing SwiftUI APIs, to debugging weird linking issues.<\/p>\n Swift Student Challenge 2025<\/a><\/p>\n There are many reasons you might want to participate in the Swift Student Challenge. Yes, 50 winners will get to attend WWDC 2025, but participation is also its own reward, too. Whether you want to build a project to flesh out your portfolio, or just want to learn something new, now\u2019s the time to get started. Submissions open on the 3rd of February and close three weeks later. That means you\u2019ve got about 6 weeks to make something amazing. Check the eligibility requirements<\/a> and get cracking.<\/p>\n Changes to server connections for Apple Pay on the Web<\/a><\/p>\n This won\u2019t affect a large number of you since it\u2019s limited to Apple Pay on the Web. That said, I\u2019d bet there are a few of you reading that\u2019ll need to make a change, or at least check that your code isn\u2019t affected. The deadline for making this change is soon, too, on February 4th.<\/p>\n Quickly paste text into a new Xcode file<\/a><\/p>\n Thanks so much to Florian Seida<\/a> for this tip for quickly making new files in Xcode. I had absolutely no idea this existed!<\/p>\n Swift 6: Typed Throws<\/a><\/p>\n Strict concurrency has tended to overshadow everything else that Swift 6 brought with it, so it\u2019s great to see Vera Dias<\/a> write up this very readable guide to typed throws. You\u2019ll learn what they are and why you should use them. Great stuff.<\/p>\n Using Copilot to write a raindrop audio synthesizer using AVAudioEngine<\/a><\/p>\n I doesn\u2019t matter if you read Matt Gallagher<\/a>\u2019s latest post because you want to hear his experience developing code with CoPilot or because you\u2019re interested in Core Audio. Either way, you\u2019re in for an interesting article. It\u2019s also really nice to see Matt back blogging again after a little break!<\/p>\n Translating an iOS\/Mac app with AI and humans<\/a><\/p>\n I\u2019ve not used generative AI to translate UI text in an app yet, but I believe it\u2019s a a step ahead of using something like Google or Apple Translate. Obviously, it\u2019s no substitute for a human translator, but depending on your app\u2019s budget you might want to check out Adam Wulf<\/a>\u2019s latest article on using AI as a starting point before moving to POEditor<\/a> to translate an app.<\/p>\n Accomplish One Thing<\/a><\/p>\n If you\u2019re struggling to get back into the swing of things this year, these wise words from David Smith<\/a> might help you:<\/p>\n The goal here is not to make massive progress; it isn\u2019t about getting back up to full speed again, going from 0 to 100 miles\/hour in one swift step. It is about building up my working inertia again. Speed is useful, but inertia is powerful.<\/p>\n<\/blockquote>\n Are you a Fira Code or an Inconsolata<\/a>?<\/p>\ncur.at<\/code> shortened links. Every link in the newsletter is now a plain and simple hypertext link that you can hover to see the URL, and I know that has been something some of you have wanted for years.<\/p>\nNews<\/h2>\n
Code<\/h2>\n
Business and Marketing<\/h2>\n
\n
And finally…<\/h2>\n