While it has always been clear that these forums are for the Swift language itself and not for Frameworks that happen to use Swift (with exceptions for the Related Projects Category), and we often have to reply to new Topics (especially in the Using Swift Category) created for off-topic subjects to explain that a given subject is off-topic, there does seem to be an unspoken exception for SwiftUI questions.
There seems to be a belief (perhaps “hope” is a better term) that SwiftUI source will eventually be opened and officially put under the umbrella of the Swift project. Perhaps this is the reason for our unwritten exception.
Create a SwiftUI Category under the Using Swift Category. While there is a swiftui tag that is being used to mark these, I think we should acknowledge the unspoken exeption the same way that Swift Composable Architecture et al. appear under Related Projects.
Put It in Related Projects
Rather than place a new SwiftUI Category under Using Swift, it could be placed under the Related Projects Category like the other related projects. I think that is a reasonable thing to do, but I also think that if we do that we will continue to get most of the SwiftUI-related posts under Using Swift, as most of these are from recent members of these forums and the Using Swift Category is an inviting beacon for newbie questions, while Related Projects reads as an advanced Category. One must also acknowledge the all-too-common misconception that SwiftUI already is a part of the Swift language itself.
Stop Allowing It
Instead of giving SwiftUI it's own sanctioned Category, we could start telling folks who create new Topics in this vein the same thing we do for questions related to UIKit, etc. and refer them to StackExchange, Apple's Developer Forums, Reddit, etc. for help. The nature of Apple's choice of names for this Framework certainly means we will continue to receive SwiftUI questions regardless of what we do, so I suspect this alternative has the most work attached as we will be frequently referring questions away.
Leave It Be
Maybe there's no need to change anything and we keep the status quo with the de facto exception for SwiftUI left unwritten.