Give your simulator superpowers

RocketSim: An Essential Developer Tool
as recommended by Apple

Issue 217
May 10, 3827

THIS WEEK'S BLOG POST
Starting May 1, 2024, apps that don’t describe their use of required reason API in their privacy manifest file aren’t accepted by App Store Connect. This week's article will be essential for you to prevent an app rejection.

SPONSORED
Pair programming in Xcode is difficult. Stop struggling to describe which line of code to change or dancing around who’s screen sharing. With Multi, simply point, draw, or even take control of your teammate’s Xcode. Multi just launched into early access, so be the first to try it out!

CURATED FROM THE COMMUNITY
Do you know when to use the overlay or background modifier over using a ZStack in SwiftUI? If not, you’ll enjoy this article by Fatbobman.
I’m a big fan of experimenting with paywalls and many of you might know the ‘famous’ Blinkist paywall that seems to be the standard. Filip Nemecek tried it out and shares positive results.
SwiftData is often connected to using with SwiftUI apps only, but you can also use it in UIKit world. This article explains how to observe for changes and connect them to a diffable data source.
While SwiftUI previews are great, they don’t always work as expected. Dominik shares an alternative in the form of hot reloading using a Swift Package.
Pie charts are new since iOS 17 and I loved how Keith Harrison builds up creating one in this article using visuals and code examples.

SWIFT EVOLUTION
An overview of last week's Swift Proposal state changes. Make sure to check them out when they're in review, as it's your opportunity to influence the direction of Swift's future.
AcceptedSE-0433Synchronous Mutual Exclusion Lock 🔒

QUESTION OF THE WEEK
This week's question comes from Thang:

How to be scalable and easy to maintain in the long term for an iOS project given we are starting today?

This has been a relevant question for everyone for years. I bet we all have examples of projects that started great but became unmanageable after months or years.

How to prevent this?
  1. Write tests.
     
    I can’t stress this enough, but tests are a great way to keep your code stable and prevent unexpected bugs. This definitely makes a project easier to maintain
     
  2. Modularity
     
    Split up your project into child packages. Focus on single responsibility and add tests within each package.

  3. Coding guidelines
     
    Either automatically or manually linted, keeping your code consistent with similar formatting makes a project easier to digest, understand, and manage.
     
  4. Documentation
     
    Even though the code you write today seems self-explanatory and ‘easy’ to understand for everyone, I bet you’ll thank your future self for writing documentation while you’re in the given context.

Like with many things, not just one thing solves this challenge. Your project will become easier to maintain when applying all these 4 rules.

Want to have your question answered next week? Ask your question on LinkedIn or Twitter.