Guides · Nov 15, 2026
Watch App Store Submission: A Solo Developer's Checklist
Summarize this with AI
Open this article in your favorite AI assistant and get a quick summary in seconds.
Submitting a WatchOS app to the App Store requires navigating specific bundle structures, screenshot requirements, and review guidelines distinct from iOS. For solo developers, understanding these details is crucial to avoid rejections and launch delays. This guide provides a checklist to package, configure, and submit your WatchOS app bundle to App Store Connect.
The guide details specific steps, from Xcode configuration to App Store Connect metadata, outlining the exact requirements for a successful submission.
Understanding WatchOS App Bundles and Targets
A WatchOS app is always bundled within an iOS app. This structure means your Xcode project will contain at least two targets: your main iOS app target and your Watch App target. The Watch App target typically includes a Watch App Extension. The Watch App target (e.g., `MyWatchApp Watch App`) manages the user interface and assets. Its associated Watch App Extension (e.g., `MyWatchApp Watch App Extension`) contains the code executed on the Apple Watch. Xcode packages these, embedding the Watch App bundle within your main iOS app's bundle.Setting Up Your App Store Connect Record for WatchOS
Before uploading any builds, prepare your App Store Connect record. Navigate to `App Store Connect > My Apps`, select your iOS app, then locate the `WatchOS` tab on the left sidebar under `App Store`. You'll need to define your WatchOS `Bundle ID` here. This should match the `Bundle Identifier` you set in Xcode for your Watch App target, which is typically derived from your main iOS app's bundle ID (e.g., `com.yourcompany.yourapp.watchapp`). Consistency here prevents common build upload errors. You must provide WatchOS screenshots. Apple requires at least one screenshot for the largest display size within each device family your app supports. This means providing screenshots for the 49mm (Ultra), 45mm, and 41mm Apple Watch sizes. You can provide up to 10 screenshots per size. For example, a 49mm screenshot needs to be exactly `1000 x 1220` pixels, while a 45mm screenshot is `934 x 1142` pixels, and a 41mm screenshot is `812 x 992` pixels. You can use LaunchShots' free screenshot editor to generate these precise sizes, ensuring they match your app's actual interface. Apple will reject screenshots that don't accurately reflect your app or are not the correct dimensions.Preparing Your WatchOS Build in Xcode
Preparing your WatchOS build in Xcode requires specific configuration. In Xcode, ensure your project's `Build Settings` are correct. For archiving, select `Generic iOS Device` as your build target, then choose `Product > Archive`. Archiving your main iOS app automatically includes its embedded WatchOS app. Check your `Info.plist` files for both your Watch App and Watch App Extension. The `CFBundleVersion` (Build Number) and `CFBundleShortVersionString` (Version Number) should be updated consistently. While bitcode is no longer explicitly required for WatchOS apps submitted via Xcode 14 or later, older projects might still have it enabled. If you're using an older Xcode version, ensure `Enable Bitcode` is set to `Yes` for all targets. Signing is a crucial step. Use `Automatic Signing` in your project's `Signing & Capabilities` tab for streamlined management of provisioning profiles and certificates. Verify that your Apple Developer Program team is selected for all targets: the iOS app, Watch app, and Watch extension.The WatchOS App Store Submission Checklist
- Archive Your App: In Xcode, select `Generic iOS Device` as the target, then `Product > Archive`. Once the Organizer opens, select your archive and click `Distribute App`. Choose `App Store Connect` as the method, then `Upload`.
- Select Build: In App Store Connect, go to `My Apps > Your App > App Store > iOS App` (or `App Store > WatchOS` if it's a new Watch-only version). Under the specific version number, select the build you just uploaded from the `Build` section. It might take some time to process and appear.
- Update WatchOS App Details: Navigate to the `WatchOS` tab.
- Screenshots: Upload your correctly sized screenshots for 49mm, 45mm, and 41mm devices. Ensure they accurately depict your app's interface.
- Promotional Text: (Optional) Up to 170 characters. Use this for timely announcements or app updates.
- Description: Up to 4,000 characters. Describe your Watch app's features and benefits. Focus on how it enhances the user's Apple Watch experience.
- Keywords: Up to 100 characters, comma-separated. These are crucial for App Store Search.
- General App Information: Go back to the main `iOS App` tab.
- Privacy Policy URL: Provide a link to your app's privacy policy. If you don't have one, consider using a LaunchShots App Privacy Label Generator to create one quickly.
- App Review Information: Provide contact details. If your Watch app requires specific login credentials or configurations (e.g., pairing with an IoT device, or a specific user account on your server), include a demo account and clear instructions. This is a frequent cause of rejection.
- Version Release: Choose whether to release the version manually after approval or automatically.
- Rating and Export Compliance: Complete the content rating questionnaire and declare any encryption usage for export compliance. This is mandatory for all apps.
- Submit for Review: Once all fields are complete and valid, the "Submit for Review" button will become active. Click it.
Common Pitfalls and Rejections for WatchOS Apps
WatchOS apps face specific scrutiny from Apple's review team due to their unique interaction model and limited screen real estate. Understanding common pitfalls can help prevent rejections. One frequent rejection is for Guideline 2.1 - Minimum Functionality. Apple wants Watch apps to be meaningful on their own, or to genuinely extend the iOS experience. If your Watch app is simply a shrunk-down version of your iPhone app without any unique Watch-specific utility, it's at high risk of rejection. For example, if you ship a habit tracker, the Watch app should allow quick check-ins, glanceable progress, or complications, not just a list of all past habits requiring extensive scrolling. Another common issue falls under Guideline 4.0 - Design. Watch apps need to be optimized for the small screen. This means prioritizing glanceable information, simple interactions, and clear, readable text. Avoid dense layouts, tiny tap targets, or complex navigation that mirrors an iPhone app. The Watch is for quick interactions, not deep dives. Incorrect screenshots are also a frequent rejection reason. Ensure your screenshots are the exact pixel dimensions required for each Watch model, are high-quality, and genuinely represent your app's current interface. Don't use placeholder images or old designs. You can also use a Screenshot Grader to get feedback on potential issues. Connectivity requirements are another area to address. If your Watch app requires the iPhone to be present and connected (e.g., for data sync), state this clearly in your App Store description and within the app. Obscuring such dependencies can lead to user frustration and negative reviews.FAQ
Can I submit a WatchOS app without an accompanying iOS app?
Yes, Apple allows for standalone WatchOS apps that do not require an iOS companion app. These apps run entirely on the Apple Watch and can be installed directly from the App Store on the Watch. However, you still upload them through your main iOS app record in App Store Connect.What are the exact screenshot requirements for WatchOS?
You need at least one screenshot for the largest display size for each device family your app supports (currently 49mm, 45mm, 41mm). The specific resolutions are `1000 x 1220` pixels for 49mm, `934 x 1142` pixels for 45mm, and `812 x 992` pixels for 41mm. You can provide up to 10 screenshots per size.Do I need a separate privacy policy for my Watch app?
Generally, no. Your WatchOS app will typically fall under the same privacy policy as your main iOS app, as data might be shared between them or handled by the same backend. However, ensure your existing privacy policy explicitly covers any data collected or processed specifically by the Watch app.How long does WatchOS app review usually take?
The review time for WatchOS apps is typically similar to iOS apps. This can vary based on reviewer workload, the complexity of your app, and whether any issues are flagged that require further investigation.What if my Watch app requires specific hardware or accessories?
If your Watch app relies on specific hardware (like a heart rate monitor you sell) or accessories, you must clearly state these requirements in your App Store description. If the app is unusable without them, the reviewer will need access to this hardware for testing, which often requires explicit instructions and potentially sending them the physical device if it's proprietary.Your Next Step
Submitting a WatchOS app successfully requires attention to detail. The most common holdup is incorrect screenshots; prioritize creating high-quality, accurately sized WatchOS screenshots after your build is ready. Use LaunchShots' free screenshot editor, which offers precise templates for every Apple Watch device, to streamline this process.Was this helpful?
Thanks — that helps me decide what to write next.
Questions or ideas?
I read every suggestion — drop yours on the feedback board.
Open feedback board →
Make your App Store screenshots free
LaunchShots is a free, in-browser screenshot maker. No signup, no watermark.
Open the app →
Comments (0)