Marco Arment

I didn't think about it.

But let me ask it to turn the cast and crew list and call sheet, which right now on iPad is one column, which is awful.

It looks terrible.

It should at least be two columns.

And I have some ideas for maybe something even more advanced than that.

But my first cut was, hey, can you just make this two column?

And it took a couple of back and forths between me and Xcode, I guess, or Claude, or I don't know how to describe this, how to verbalize this.

But it took a couple of back and forths and it got it to the point that visually it was exactly what I wanted.

And that only took, I don't know, 10-ish minutes, something like that.

It really was not long at all.

But functionally, it was a mess.

And the particulars don't matter.

But suffice it to say, it totally screwed up navigation.

A lot of things were hosed.

And I've heard rumblings that these things don't do too well with SwiftUI.

And the theory is in part because SwiftUI is a moving target, in part because it's so new.

But one way or another, I can tell you that I was not exceedingly impressed by that experience.

And additionally, shoot, now I'm drawing a blank as to what it was, but there's something else I had to do that was much less invasive.

Golly, it's really going to drive me nuts because I can't remember what specifically it was, but something in call sheet.

And I wanted it to do something and, oh, I think I needed it to pump or to pipe a date from, you know, like high up in the object graph to deep within the object graph.