Join 31,000+ Swift & iOS developers — free, every Tuesday, in 5 minutes.
Almost there — check your inbox to confirm your subscription.
No spam. One email every Tuesday. Unsubscribe in one click.
This article has been awaited by many of you. I constantly postponed writing about my workflow since I felt like I was still learning, I wasn't ready to recommend anything yet. The reality is that I'm learning more than ever, and this won't stop. Therefore, I decided to check-in with you today, to teach you what I've learned so far.
Read the articleAre you tired of Ruby and Fastlane installation issues? There's got to be a better way! Discover Codemagic open source CLI tools. It is not a drop-in replacement for all of what Fastlane does (screenshots for example), but we use it at Codemagic to build and publish iOS and Android apps, also versioning and device provisioning. View on GitHub.
Learn moreI’ve been using UUIDs for a long time, but really didn’t know how they work behind the scenes. Thanks to this detailed post by Omar Elsayed, I finally know!
Writing code to use Foundation Models is one thing, but properly prompting is a whole other skill. Artem Mirzabekianis here to help you out.
I honestly never think about access levels for my imports, but I realize that’s mostly a knowledge problem. This article by Alexander Weiss helped me revisit this behavior.
You’re happy to finally get them working, you test them using RocketSim, but that’s only the beginning. I recognize these issues from my time at WeTransfer, and I’m happy that Alberto De Bortoli is sharing their solutions with us.
What if you run into an annoying issue that costs you hours to fix? You spent 18 months getting a PR merged and improving the Swift compiler. Or at least, that’s what Matt eventually did, and he’s sharing his story with us.
It’s these neat little extensions that sometimes can make a big impact in the beauty of Swift we write. Thanking Natalia Panferova for this tip!
Last week's Swift proposal state changes. Review-stage proposals are your chance to influence Swift's future.
Related article: Introducing AI prompts and recording metadata.
More and more teams are finding their way to RocketSim. Our churn is low, and many clients renew with more seats. The biggest team using RocketSim is now using 150+ seats and counting.
It's clear that we have a purpose in the app development ecosystem, but I also don't want to stop here. I've been researching a lot last week on where to go next. I mention a RocketSim CLI before, RocketSim MCP, I've been exploring deeplinks for AI tools to execute, there's a lot!
My goal is to let RocketSim connect the Simulator to AI development tools like Cursor. There are many open-source frameworks for this, or MCP servers to use, but I feel like we have a unique position. We're sandboxed, in the App Store, and we already have data like build insights and networking requests stored locally.
The first result of this research is an actual feature that's available in the latest release. The Network Monitor now allows you to export the network requests from the current session into a prompt, ready to use in an AI Agent of choice.
The network requests are redacted, leaving only the minimal required information in the prompt. This reduces tokens, but also prevents leaking API keys, auth tokens, or user data into agents.
Obviously, the next step would be to serve this data through something like an MCP server. I'm exploring the latter, but meanwhile, I'm preparing the app for the future of RocketSim.
Join 31,000+ Swift & iOS developers and get the next one in your inbox — free, every Tuesday, in 5 minutes.
Almost there — check your inbox to confirm your subscription.
No spam. One email every Tuesday. Unsubscribe in one click.