For complications that display data from the iPhone app, is pushing updates from the phone still the right model, or should complications fetch independently on the watch when connectivity is available?

When a voice assistant needs clarification or disambiguation, is spoken dialog alone sufficient under the rule that voice-based conversational apps must not show text or imagery in query responses? or is there an approved pattern (action buttons, short lists) within the template depth limits?

When a widget opens a specific screen in the main app, what’s the best way to pass structured state — like an item ID, date, and scroll position — so navigation works on cold launch and doesn’t conflict with an existing navigation stack?

For data that changes throughout the day, like weather or schedules, what’s the most reliable refresh strategy for WidgetKit: timeline policies, background tasks, push notifications, or user-driven reloads?

If the main app isn’t fully SwiftUI, but you also ship native SwiftUI widget extensions, watch complications, and a watchOS app, what’s the recommended way to share models, formatting, and chart logic across those targets without duplicating code?

Can Siri’s conversational features in CarPlay invoke third-party App Intents without the user opening that app’s CarPlay tile? e.g. “Hey Siri, ask [App Name] …”?

What does Apple look for when approving carplay-voice-based-conversation for a vertical, task-focused assistant (not a general AI chatbot)? Are there specific driving-safety expectations, and can subscription-gated actions be enforced inside perform()?

For a domain-specific voice assistant (not navigation, not general-purpose chat), should we integrate via the CarPlay voice-based conversational entitlement, Siri + App Intents/App Schemas, or a hybrid? What does Apple recommend?