Chris Eidhof

In SwiftUI, you can often achieve the same thing in many different ways.

I’ve been working on an experimental project with a friend, a static analyzer.

In our recent SwiftUI workshops, we have told people at the start to not use an LLM during the workshop.

I just launched the FormatStyle Guide, a new project that explores Swift Foundation’s FormatStyle APIs in the browser via WebAssembly.

In 2013, I got rejected for Apple’s “Tech Talks”.

In January, Nathan and I built a Mac app over the course of a month.

Over the last weeks, I’ve been experimenting with building agents.

The other week I met Orta again.

This month, I want to focus on using LLMs more, and AI in general, so I’m working on a bunch of projects.

This has been a very eventful year for me personally.

When you write SwiftUI views, one of the big advantages over UIKit is that SwiftUI performs automatic dependency tracking.

When I have an LLM assistant write prototypes in a language that I don’t know, my prompts are high-level and focused on features, not implementation.

I teach SwiftUI for a living.

I gave a talk about my understanding of the Attribute Graph.

When we cover SwiftUI’s state system in our workshops, we often get asked: How can I set up my view model in a view?

For the last few years SwiftUI’s alignment guides have been broken in combination with if-statements.

In SwiftUI, there are two kinds of bindings.

In our SwiftUI workshops, we often see people reaching for the Group view.

I noticed that phase animators weren’t behaving as expected, and I initially assumed I’d found a bug in SwiftUI.

Just to be consistent I’ll add the notes for this week as well.