iOS Resources
Hand-picked Articles and Videos

A video enhancement feature usually starts with a product sentence: “Can we make playback look sharper?”The engineering answer should not start with “add a filter.” It should start with a boundary question: where in the playback pipeline are we allowed to touch the frame?

Recently, I was asked an interesting question. If the purpose of an actor is to protect mutable state, is a stateless actor pointless?

At first, I thought it was an easy answer. Actors exist to define a little, protective bubble around state. They "isolate" data away from any unsafe accesses. An actor that has nothing to isolate seems like a strange thing.

Can such an arrangement serve a purpose?

Swift makes it easy to write clean camera and video code. It also makes it easy to accidentally destroy performance with one innocent conversion.

The declarative expression of animation is one of SwiftUI’s core strengths. But in some scenarios the result isn’t always as smooth as we’d hope. A typical example: when the content height inside a List row changes dynamically — a subtitle going from empty to non-empty, or text changing its line count after an update — the system’s built-in layout engine often fails to produce a continuous transition. Instead we get visible height jumps, flicker, or even clipping anomalies. This article starts from that phenomenon, peels back the causes layer by layer, and gives a solution built entirely on SwiftUI’s native primitives. Along the way it revisits a few key constraints in SwiftUI’s layout machinery.

Xcode 26.3 introduced agentic coding support with Claude Agent, OpenAI Codex, and MCP. This is not just smarter autocomplete. Apple describes it as a workflow where agents can work with more autonomy toward a developer’s goals, use Xcode tools, inspect project structure, run builds, search documentation, and iterate through fixes.

ou may think about defer keyword as one of the most ambiguous language features in Swift, but it is very useful in some cases. You can use it deliberately, and it will give you safety. This week we will talk about some best practices of using defer in Swift.

I have never published a WWDC wishlist, or ever even really thought much about one before. But, there are some areas that I'm definitely interested in, so I thought it would be fun to share.

Here's my "watchlist" of things I'll be paying special attention to.

I thought App Intents was going to be a Siri feature, but It turned into an architecture audit.The weirdest part wasn’t writing the intents. It was debugging failures with almost zero visibility.Six shortcuts defined. Two appeared. No logs. No errors. Just missing tiles in Shortcuts.app.

Shortcuts launches your app headlessly. App.init never runs. If your entity queries depend on app-registered services or SwiftData setup, the system can silently drop the shortcut entirely.

Swift Concurrency provides modern tools for handling asynchronous code through async/await, actors, and structured concurrency. Following best practices ensures your concurrent code is safe, efficient, and maintainable.

‍