NavigationView is deprecated. You can use NavigationStack and NavigationSplitView instead. Here you can find more details.

Make sure to check if your app builds and runs on Swift Playgrounds.

Thanks! I reviewed the options, and I was wondering which run destination (not target, sorry) will be used when choosing the Xcode option. I was worried about an issue I had with a SwiftUI NavigationSplitView in Mac Catalyst (FB12108868), but I found a workaround and I don't think I'll have any specific instructions.

i'm not Quinn, but I'd say what I think. The expression is a closure passed in the set: parameter of the initialiser. You need to pass a closure that takes a newValue parameter (of the T type as in Binding, which here is Bool) as input, and set it to whatever other variable you use. You use another variable to store the binding's actual value, and this value is of type MyBool.

No problem! Yeah, I figured out maybe that's what happened. For a moment, I read it that way too :)

I was going to make a new post about this, but fortunately I found this thread. It seems that the less-than sign is still not fixed, but I think you know that :) Maybe this happens within some kind of cross site scripting protection? Just a guess...

Weird... For me, on Safari (macOS) it does't work either (tried private browsing window too). The Reply and Add a Comment buttons are there but they don't do anything when clicked.

Yeah, same for me. There's no Reply textbox.

It seems that it doesn't work on other browsers either.

Perhaps the thread allows only Apple-employee accounts to comment

Sorry, I meant bottom left corner.

Happy to help. Good luck with your submission!

Must note that may be cases when App Playgrounds built with Xcode won't run in Swift Playgrounds, and the other way around (for example, see this thread). Check if your app runs fine on Swift Playgrounds on macOS.

Oh... Well, that definitely shouldn't have happened.

Yes, it is, provided that you comply with the terms. An iPad / Mac app is in the scope of the challenge, so you can use them. Other than that, make sure you're not using them (or other "substantially or confusingly similar" symbols) for "logos, app icons or other trademark-related use".