Enable device capabilities for a Universal Windows Platform app

This topic explains how to declare device capabilities in Microsoft Visual Studio to use cameras, microphones, location sensors, and other devices for a Universal Windows Platform (UWP) app.

Specify the device capabilities your app will use

Windows apps require you to specify in the app package manifest when you use certain types of devices. In Visual Studio, you can declare most capabilities by using Manifest Designer or you can add them manually as described in How to specify device capabilities in a package manifest (manually). This tutorial assumes you're using Manifest Designer.

Note

Some types of devices, such as printers, scanners, and sensors, don't need to be declared in the app package manifest.

• In Visual Studio Solution Explorer, double-click the package manifest file, Package.appxmanifest.
• Open the Capabilities tab.
• Select the device capabilities that your app uses. If you don't see the capability you're looking for in Manifest Designer, add it manually. For more info, see How to specify device capabilities in a package manifest.

Device Capability	Manifest Designer	Description
AllJoyn		Allows AllJoyn-enabled apps and devices on a network to discover and interact with each other. App apps that access APIs in the Windows.Devices.AllJoyn namespace must use this capability.
Blocked Chat Messages		Allows apps to read SMS and MMS messages that have been blocked by the Spam Filter app.
Chat Message Access		Allows apps to read and delete Text Messages. It also allows apps to store chat messages in the system data store.
Code Generation		Allows apps to generate code dynamically.
Enterprise Authentication		This capability is subject to the Microsoft Store policy. It provides the capability to connect to enterprise intranet resources that require domain credentials. This capability is not typically needed for most apps.
Internet (Client)		Provides outbound access to the Internet and networks in public places like airports and coffee shops. For example, Intranet networks where the user has designated the network as public. Most apps that require Internet access should use the capability.
Internet (Client & Server)		Provides inbound and outbound access to the Internet and the networks in public places like airports and coffee shops. This capability is a superset of Internet (Client). Internet (Client) doesn't need to be enabled if this capability is also enabled. Inbound access to critical ports is always blocked.
Location		Provides access to the current location. This is obtained from dedicated hardware like a GPS sensor in the PC, or derived from available network information.
Microphone		Provides access to the microphone's audio feed. This allows the app to record from connected microphones.
Music Library		Provides the capability to add, change, or delete files in the Music Library for the local PC and HomeGroup PCs.
Objects 3D		Provides programmatic access to the user's 3D Objects, allowing the app to enumerate and access all files in the library without user interaction. This capability is typically used in 3D apps and games that need to access the entire 3D Objects library.
Phone Call		Allows apps to access all of the phone lines on the device and perform the following functions: place a call on the phone and show the system dialer without prompting the user; access line-related metadata; access line-related triggers. Allows the user-selected spam filter app to set and check the block list and call origin information.
Pictures Library		Provides the capability to add, change, or delete files in the Pictures Library for the local PC and HomeGroup PCs.
Point of Service		Provides access to Point of Service peripherals. This capability is required to access APIs in the Windows.Devices.PointOfService namespace.
Private Networks (Client & Server)		Provides inbound and outbound access to Intranet networks that have an authenticated domain controller, or that the user has designated as either home or work networks. Inbound access to critical ports is always blocked.
Proximity		Provides the capability to connect to devices in close proximity to the PC via near-field communication (NFC). Near-field proximity may be used to send files or communicate with an app on the nearby device.
Removable Storage		Provides the capability to add, change, or delete files on removable storage devices. The app can only access the file types on removable storage that are defined in the manifest using the File Type Associations declaration. The app can't access removable storage on HomeGroup PCs.
Shared User Certificates		This capability is subject to the Microsoft Store policy. It provides the capability to access software and hardware certificates, such as smart card certificates, for validating a user's identity. When related APIs are invoked at runtime, the user must take action (insert card, select certificate, etc.). This capability is not necessary if your app includes a private certificate via a Certificates declaration.
User Account Information		Gives apps the ability to access the user's name and picture. This capability is required to access some APIs in the Windows.System.UserProfile namespace.
Videos Library		Provides the capability to add, change, or delete files in the Videos Library for the local PC and HomeGroup PCs.
VOIP Calling		Allows apps to access the VOIP calling APIs in the Windows.ApplicationModel.Calls namespace.
Webcam		Provides access to the built-in camera or attached webcam's video feed. This allows the app to capture snapshots and movies.
USB		Provides access to custom USB devices. This capability requires child elements. This feature is not supported on Windows Phone.
Human Interface Device (HID)		Provides access to Human Interface Devices (HID). This capability requires child elements. For more info, see How to specify device capabilities for HID.
Bluetooth GATT		Provides access to Bluetooth LE devices through a collection of primary services, included services, characteristics, and descriptors. This capability requires child elements. For more info, see How to specify device capabilities for Bluetooth.
Bluetooth RFCOMM		Provides access to APIs that support the Basic Rate/Extended Data Rate (BR/EDR) transport and also lets your UWP app access a device that implements Serial Port Profile (SPP). This capability requires child elements. For more info, see How to specify device capabilities for Bluetooth.

Use the Windows Runtime API for communicating with your device

The following table connects some of the capabilities to Windows Runtime APIs.

Device Capability	API
AllJoyn	Windows.Devices.AllJoyn
Blocked Chat Messages	Windows.ApplicationModel.CommunicationBlocking
Location	See Maps and location overview for more information.
Phone Call	Windows.ApplicationModel.Calls
User Account Information	Windows.System.UserProfile
VOIP Calling	Windows.ApplicationModel.Calls
USB	Windows.Devices.Usb
HID	Windows.Devices.HumanInterfaceDevice
Bluetooth GATT	Windows.Devices.Bluetooth.GenericAttributeProfile
Bluetooth RFCOMM	Windows.Devices.Bluetooth.Rfcomm
Point of Service	Windows.Devices.PointOfService