Wild. Does the conversation feel intuitive with the editAsset schema?

I would say don’t bother filing enhancements. Apple had several years to improve this experience and did not.

I’ll echo this. I don’t know why the communication about this feature set is so detached from the development experience. Maybe it’s working fine in internal builds, but I haven’t seen it yet.

That's what makes the menu bars so weird. What "State" populates a menu bar button action handler? It's just a weird concept, but understanding it can allow you to disable/enable menu bar buttons as needed.

Notifications can work! Just know that if you do ever spawn multiple windows that notification will be caught by each one. Good on you for trying out a new framework. It requires a different kind of thinking, and has quite a few quirks lurking in the shadows. You gotta remember that at any given moment in time the entire UI of your app should be rebuildable from the ground up off of state that is maintained outside and inside(@State) of views.

The FocusedWindowSheet in my app is: public enum FocusedWindowSheet: Hashable, Identifiable { public var id: Self { self } case settings case addFolderGallery(...) } My enum fuels a standard sheet to show via the "item" presentation mechanism.

LOL "Foused" are typos of "focused". I never noticed. FocusedWindowSheet is used in my example, but it can be whatever triggers the import window in your content view. It looks like in this case it can be "Bool" since it relies on isPresented.

Yeah, step one, imo, is to get that .fileImporter onto the contentView that actually acts on the file. Make it work when spawned from a tool-bar button to get started. I don’t like that thing living at the App level either.

No custom schemas. “file a feedback request”. No, apple won’t compensate us for filing feedback requests, but they will take 30% of revenue generated by your app.

The devs in the group lab seemed to indicate that Siri AI would not interpolate phrasing to trigger shortcuts provided via the AppShortcutsProvider. Is this functionality supposed to be in Beta 3? (It’s not)

Same. Even looked into “open file” or “moveFile”, but documentation says that Siri doesn’t even use those. Only shortcuts. https://developer.apple.com/documentation/appintents/appschema/filesintent/openfile

If you build the intent to answer questions about properties on the building entity, would you be able to invoke it conversationally? Or would you be limited to phrases that rigidly defined in the 10 shortcuts that apps can make available In their shortcuts provider?

I don’t think Spotlight uses the view-hierarchy based AppEntity declarations. As far as I understand it, Spotlight only sees what’s provided to CoreSpotlight directly?

Okay, I think I've isolated it more. My "hops like crazy" scenario was multiple LazyVGrids inside a single ScrollView. I'm going to assume that's not a supported configuration. I've attached a project and some videos to FB23182374 . Let me know if you have any questions or want me to try some things out on it.

Yeah. I'm at my wits end. I was hoping to unify some NSCollection and UICollection view code, but i don't think it's meant to be. Of course a sample project I made doesn't bounce near as much, making me even more confused.