@e2aab4fb this may have changed (and seeing how api comes and goes and is randomly renamed in SwiftUI, it likely is team specific) in the past all api needed to be vetted and a specific need for it had to be justified and lobbied for before anything was made public.

It’s the only way that api can be invested in and be guaranteed to exist for years to come. 

 @29b4f570 Oh yeah, API review is still extensive, and I know they give every small change a huge amount of thought. If anything I'm just hoping maybe to direct their attention to specific pain points across an extremely large API surface.