---
title: Migrating to a single-target watchOS app
framework: watchos-apps
role: article
role_heading: Article
path: watchos-apps/migrating-to-a-single-target-watchos-app
---

# Migrating to a single-target watchOS app

Adopt the single-target configuration to simplify your project and avoid ambiguity about where to store resources and apply entitlements.

## Overview

Overview A watchOS app has one of the following project configurations: Single-target apps have a simpler project configuration and avoid ambiguity about where to store resources and apply entitlements. note: Both single-target and dual-target apps can include other targets. For example, you can add a target to implement widgets or app intents. When the minimum deployment target is watchOS 9.2 or later, building a dual-target app with Xcode produces an error, and prompts you to migrate to a single-target app using the built-in migrator. Building a single-target app that still uses the  WKExtension APIs produces warnings that guide you to replace the APIs with the WKApplication counterparts. If you have a dual-target watchOS app, migrate it to a single-target app. Convert a dual-target app to a single-target app Follow these steps to convert your app: Create a complete backup of your project before you start, so you can roll back if something goes wrong. In the Project navigator, select your project, then choose Xcode > Editor > Validate Settings. Select the “Project <your project> - Upgrade <your watchOS app target> to a single-target watch app” checkbox if it’s unselected, then choose Perform Changes. If you use storyboards, update the class module for each interface controller to the watchOS app module. Select an interface controller, choose View > Inspectors > Identity, then set the Class field in the Custom Class section. Repeat for each interface controller. Remove any files that only apply to the WatchKit extension, such as the extension’s information property list. Reorganize the groups and files in the Project navigator to clean up your project. Run the project on an Apple Watch to verify everything works. The second step removes the WatchKit extension target and moves its source code and resources to the watchOS app target. At the code level, it replaces WKExtension and WKExtensionDelegate with WKApplication and WKApplicationDelegate. It also updates the watchOS app target’s information property list as needed. For example, if your watchOS app has a complication, it moves the complication controller class, which is specified with CLKComplicationPrincipalClass, to the watchOS app target, and adds the CLKComplicationPrincipalClass and CLKComplicationSupportedFamilies entries to the watchOS app’s information property list.

## See Also

### Essentials

- [Creating an intuitive and effective UI in watchOS 10](watchos-apps/creating-an-intuitive-and-effective-ui-in-watchos-10.md)
- [Updating your app and widgets for watchOS 10](watchos-apps/updating-your-app-and-widgets-for-watchos-10.md)
- [Building a watchOS app](watchos-apps/building_a_watchos_app.md)
- [watchOS updates](updates/watchos.md)