Adding an Apple Watch App
Your Draftbit mobile app can include an Apple Watch app. It lives in the same project and ships inside your iOS app, so anyone who installs your app from the App Store can add it to their watch. The AI Agent writes it for you.
A watch app is built differently from the rest of your project. Your phone screens are React Native, which doesn’t run on Apple Watch, so the agent writes the watch screens in SwiftUI, Apple’s own UI framework. Know these limits before you start:
- You can’t preview the watch app in Draftbit. The in-browser preview, the Draftbit Preview app, and the simulators show your phone app only. You see the watch app for the first time on a real Apple Watch, through TestFlight.
- You change it through AI Chat. Selecting and editing elements in the Preview Panel works on your phone screens, not on the watch app.
- Android watches aren’t covered. Draftbit doesn’t support Wear OS apps.
Before you begin, make sure you have:
- A mobile app in Draftbit
- iOS publishing set up for the app, which needs the Standard plan or above
- An Apple Watch paired with the iPhone you test on
1. Ask the AI Agent to build the watch app
Section titled “1. Ask the AI Agent to build the watch app”Describe what the watch app should show and do in AI Chat. Watch apps work best when they do one or two things at a glance, so start small:
“Add an Apple Watch app to this project. It should list today’s appointments from our API, and tapping one should mark it as done. Use the same accent color as the phone app.”
The agent adds a targets/watch folder to your project with the watch app’s code, and turns it on in your app’s configuration. Your phone app keeps working the same way in the preview.
Tell the agent where the watch app’s data comes from. There are two options, and the agent can combine them:
| Source | How it works | Good for |
|---|---|---|
| Your backend | The watch app calls the same API or database your phone app uses, over its own internet connection. | Data that already lives on a server, such as orders, bookings, or messages. It works even when the phone isn’t nearby. |
| The phone app | The phone app sends data to the watch through Apple’s Watch Connectivity. This adds a native package to your phone app. | Data that only exists on the phone, and passing a signed-in session to the watch so people don’t have to log in twice. |
2. Register the watch app’s Bundle ID
Section titled “2. Register the watch app’s Bundle ID”Apple signs the watch app separately from the phone app, so it needs its own Bundle ID. It’s your app’s Bundle ID followed by .watch. If your app is com.example.appname, the watch app is com.example.appname.watch.
Register it in your Apple Developer account the same way you registered your app’s own Bundle ID. Follow Create a Bundle Identifier, and enter your app’s Bundle ID followed by .watch.
You only do this once. You don’t need a second app in App Store Connect: the watch app is part of your iOS app’s listing.
3. Publish to TestFlight
Section titled “3. Publish to TestFlight”Publish to the App Store destination the way you normally do. See Publish Your App. Draftbit builds the watch app together with your phone app, signs both, and uploads them to App Store Connect as one build, which then appears in TestFlight.
4. Install it on your watch
Section titled “4. Install it on your watch”Open TestFlight on the iPhone paired with your watch and install the build. Then open the app’s details page in TestFlight. When the watch app is compatible with your watch, a button to install it appears there.
When you want changes, ask the agent, publish again, and update the build in TestFlight. Over-the-air updates don’t reach the watch app, so every watch change needs a new build.
Troubleshooting
Section titled “Troubleshooting”The publish fails with a signing or provisioning error that mentions your .watch Bundle ID. The watch app’s Bundle ID isn’t registered in your Apple Developer account, or it’s spelled differently from the one in the error. Go back to step 2, then publish again.
The publish fails while building the watch app. Draftbit can’t check the watch app’s code while the agent writes it, so a mistake in it first shows up as a failed build. Open the failed publish on the Publishing page, select View Failure Summary, then Ask the assistant to fix it.
You want to catch build errors before publishing. On the Pro plan, building the iOS simulators builds the watch app too. The simulator still shows only your phone app, but a simulator build that succeeds means the watch app’s code compiles.
The watch app doesn’t show the phone app’s data. If the watch app gets its data from the phone, open the phone app at least once so it can send that data. Ask the agent to show an “Open the app on your iPhone” message on the watch until data arrives.