AppIntents-friendly WatchOS Companion App

Question

Created 1d

Replies 5

Boosts 1

Participants 2

This post is from the WWDC26 watchOS Q&A.

I have a Siri/widget-oriented app that would benefit from some sort of watchOS presence and I am trying to figure out the best approach. Can you help me understand the current options available? Initially I thought there was a kind of watchOS app that depended on an iPhone for nearly everything, but I am not clear if that approach has been deprecated. My app uses CloudKit for storage and is intended to be friendly to multiple devices, so theoretically the watch could stand on its own but in terms of staying closely in sync with the phone I am not clear that is the best approach. Further, it would seem to me better for Siri requests on the watch to directly update the phone if that were possible.

My app heavily uses AppIntents, currently within the iPhone target. I am unclear if using an AppIntent extension would be a good path. I have found limited information about these extensions.

I did an experiment with AppIntents in a watchOS app and had a lot of trouble getting the watch to recognize my shortcut phrases (or even to show the shortcuts in the watch Shortcuts app).

With all of this in mind, can you offer me some recommendations about architecting a watch-friendly AppIntents approach.

Answered by Frameworks Engineer in 891456022

For the Siri interactions, are you currently using App Shortcuts in your iOS app?

For Widgets in the Smart Stack, you'll need a watch app with a widget extension. We have several good WWDC session with information on Widgets + Smart Stack, including WidgetKit Foundations and What's new in watchOS 26. If you have widgets in your iOS app, you know most of the concepts and there are a few specifics in there for Smart Stack recommendations.

Since you have your data in CloudKit, the paired phone doesn't need to be nearby. CloudKit should keep your data in sync. You can use Watch Connectivity to keep the widgets on Apple Watch up to date (see WCSession.transferCurrentComplicationUserInfo(_:). Otherwise, you're relying on timeline updates to keep the information timely on your widgets.

Answer 1

Frameworks Engineer OP

Apple

1d

To help us answer this, what are your goals with your watchOS app? Are you attempting to create an Apple Watch-friendly version of your iOS app? Or are you trying to integrate only some Siri functionality?

Answer 2

aharriscrowne OP

1d

The most important thing is being able to speak multi-step Siri interactions that generate new records, which include location services, btw. Second most important is timely widgets in the user‘s Smart Stack. And beneficial but not necessary is an app the user can open on the watch with up-to-date info and user input.

I have honestly not given thought to whether those things could happen without a paired phone nearby, but I can imagine users benefitting from that.

Answer 3

Frameworks Engineer OP

Apple

1d

Recommended

For the Siri interactions, are you currently using App Shortcuts in your iOS app?

For Widgets in the Smart Stack, you'll need a watch app with a widget extension. We have several good WWDC session with information on Widgets + Smart Stack, including WidgetKit Foundations and What's new in watchOS 26. If you have widgets in your iOS app, you know most of the concepts and there are a few specifics in there for Smart Stack recommendations.

Since you have your data in CloudKit, the paired phone doesn't need to be nearby. CloudKit should keep your data in sync. You can use Watch Connectivity to keep the widgets on Apple Watch up to date (see WCSession.transferCurrentComplicationUserInfo(_:). Otherwise, you're relying on timeline updates to keep the information timely on your widgets.

Answer 4

aharriscrowne OP

1d

Thanks for the reference materials

Yes I have a Shortcuts provider in my iOS target currently

Answer 5

Frameworks Engineer OP

Apple

1d

Accepted Answer

Adding a Shortcuts Provider to your watchOS app should make your Shortcuts appear in the Shortcuts app in watchOS, and should make them available to Siri. If that doesn't work, please file feedback.

I've noticed that watchOS is pickier about recognizing the phrases with App Shortcuts, so I usually use a different Shortcuts Provider for my watchOS app and provide a few more phrases. The phrases need to be simple and memorable.