Run iOS builds on M1, Intel or both with Orka
Orka 2.0 is now available and includes support for macOS build and test VMs on Apple silicon (M1) nodes – either as a fully ARM-based environment or combined with Intel nodes to create a hybrid cluster. Learn more.
Swift bugs are moving to GitHub Issues and we need your help
While the Swift project lives on GitHub, it always felt odd to use a JIRA instance for bugs. That's all changing, but the Swift team needs your help to ensure a smooth transition. If you've ever filed a bug on the JIRA instance, ensure it stays attributed correctly by filling in your JIRA and GitHub usernames on your Swift forums profile. There are more details in the post, so give it a read.
Swift Evolution Monthly
I was sad to see the Swift Weekly Brief go back on hiatus at the end of last year (I'm refusing to say it's dead, as I still hope someone will continue it). This new newsletter from Cihat Gündüz might fill the gap, though! It also covers news from Swift Evolution and the Swift open-source project and goes into even more depth than the Weekly Brief did! It may even be a little too long. 😅 This is Issue 1, so you should subscribe!
SwiftLint for Swift 5.6
I don't link to SwiftLint enough in this newsletter. It's one of the best tools you can add to your projects, and it has been tirelessly maintained since 2015 by a dedicated core team. Here's JP Simard with some details on the latest release, ready for Xcode 13.3 and Swift 5.6.
If you've ever used the Unix
time command, the functionality of this new tool from Marin Todorov will be familiar, but it's more than it initially seems. Yes, having timing information in a window is nice, but if you run the tool via
sudo, it also shows memory, CPU load, and signpost information. It's early days, but I can see this being useful.
I need to look into this new Xcode 13.3 tool that Daniel Martín noticed in more detail, but it looks potentially interesting. Or, maybe Daniel will write up a blog post that I can link to next week? 🤷♂️😂
This new package from Morten Gregersen is worth a look for two reasons. First, it’s an API client library for the App Store Connect API, and that’s always useful. However, what makes it unique is that it’s powered by code generation run via a GitHub Action. So, whenever the API changes and the OpenAPI specification gets updated, the action generates a new pull request, so it’s always up-to-date! Whatever next! 🤑
Using the new KeyboardLayoutGuide API
Avoiding the keyboard has been a problem we've been dealing with since day one of the iPhone SDK, and while it's nowhere near as painful these days as it was in those early days, that didn't stop Apple from adding a new API in iOS 15 to make it even easier! Let Leonardo Pugliese teach you all about it.
Solving Small Problems with Small Tuples
Does Jordan Morgan like tuples? Why, yes, he does!
Every Screen in Your App Should Be a Scrolling View
I agree with Michael Amundsen.
iOS Developer @ Konrad Group – Konrad is an amazing community of the brightest minds in tech. We build bleeding edge mobile applications for some of the largest, most exciting companies in the world. We have a team of 250+ developers that work with the latest technologies. – Remote (within US timezones) with some on-site work (Canada)
Mid-Senior iOS Software Engineer @ Nelnet Community Engagement – At NCE, we believe in the power of community-minded organizations. We help those organizations grow their impact by making it easy to engage anytime, anywhere. We help schools, churches, & nonprofits engage their communities through text, web, & branded apps. – Remote (within US timezones) or on-site (United States)
Senior iOS Developer @ Komoot – Touching all parts of the iOS app, your work will make outdoor adventures easily accessible to our users. You’ll develop diverse features for navigation, routing, social interaction and content visualization that will make your work challenging and fun. – Remote (within European timezones)
What happens when an About window reaches its final form? 🚀
I love this so much. I miss the days when there were more quirky and weird things in computing.
If you’ve visited iOS Dev Jobs over the last couple of months, it might look the same as when it re-launched, but it’s not! I thought it was time for a quick update on some improvements since the new site went live.
There are new features, like filtering jobs on the web version (The original only had filtering for the email and the apps), additional information about each job, like whether a position is full-time/part-time or contract/permanent. Loads of bug fixes and other minor features, like payment via invoice. But there’s one new feature that I think is worth discussing in more detail—collecting compensation information.
Soon after the re-launch last August, Sophie Lambrakis tweeted me advocating for the site to collect compensation information. I had thought about it, but if I’m honest, I knew getting companies to provide that information voluntarily would be challenging, and I wanted to get the basics right first.
Talking openly about compensation can be uncomfortable. In my experience, it’s rare to discuss it with friends, and even more so with co-workers. That said, things are slowly changing, as Jordan Rose’s post from earlier this week illustrates.
Companies have also been reluctant to set expectations around remuneration, although I believe that there are significant benefits in being more transparent. Setting realistic expectations will pre-filter applicants, but it also speaks volumes about how a company thinks about pay equity and fairness. It’s a hugely positive indicator amongst people looking for a new job.
So, I added the field, and then the real work started! I struggle to remember the last time I obsessed over some in-app copy as much as I did about the preamble and help text for this question. I even tweaked it twice today as I wrote this! 😬 There’s no way I could continue to run a successful site if it were a mandatory field, but I hope that by encouraging companies to post this information, I’m helping move things in the right direction.
Since the feature went live about a week ago, only one company has filled in that field. 😅 That’s probably entirely predictable, but I think they deserve recognition for doing it, so please go and check out the job listing for Nelnet Community Engagement. They’re doing plenty of things right in their job description, too.
Is your company hiring? You can post jobs for free, and while I can’t promise you’ll get a massive shout out like that if you include compensation information, I can promise you’ll make people think better of your company when they’re considering applying for your job.Dave Verwer