Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.
URI associations for Windows Phone
This article explains how to associate your application with an URI scheme in order to launch it when interaction with such URI is detected.
- URI associations for Windows Phone
- URI Association Schemes List (known schemes)
- Designing URI scheme handlers
- URI schemes for launching built-in apps for Windows Phone 8
- Reserved URI scheme names
- Windows Phone DevCenter URI Association Sample
Windows Phone 8 introduces the possibility for your app to register to a predefined kind of URI scheme. This will allow you to launch your application from various sources and with various optional parameters. The URI will have to be formatted as follows:
<Custom Protocol Name>:<The landing page>?[First parameter name]=[First parameter value]&[Second parameter name]=[Second parameter value]
Note that its not mandatory to put the landing page after the semi colon, but it is a good practice. You can use an ID like this:
How to register for an URI association
To register an URI scheme for your app you will have to manually edit the app manifest. In the Solution Explorer open the Properties folder, right click on the WMAppManifest.xml file and select View Code. Scroll down to the end of the Tokens element and after it add an Extensions element with a Protocol children like this:
<App ... >
<Protocol Name="myappuri" NavUriFragment="encodedLaunchUri=%s" TaskID="_default" />
Just replace myappuri value with the URI you want to use. The other parameters are mandatory and must stay like this.
What URI scheme should I use?
To ensure you don't accidentally re-use a URI reserved by the operating system or default applications or a URI registered to another third party app, we recommend you include your company and app name in your URI as shown (see Designing URI scheme handlers for more detail):
Tip: Don't forget to document your app URI scheme and include it in our URI Association Schemes List.
Developers can also create and use protocols that are intended for general "classes" of apps. For example, developers of Calendar apps might agree a common protocol, and allow end-users to determine what app they choose to download or use as the handler. Note that there is nothing to stop developers using any protocol that isn't reserved for the default apps/operating system.
How to detect that your user launched the app from the URI association
You will have to implement a custom UriMapper that will parse the Uri at the launch of your application and try to detect the source. Following the sample provided above, the UriMapper would look like this in our case:
class AssociationUriMapper : UriMapperBase
private string tempUri;
public override Uri MapUri(Uri uri)
tempUri = System.Net.HttpUtility.UrlDecode(uri.ToString());
// URI association launch for my app detected
// Get the category (after "Category=").
int categoryIndex = tempUri.IndexOf("Category=") + 9;
string category = tempUri.Substring(categoryIndex);
// Redirect to the MainPage.xaml with the proper category to be displayed
return new Uri("/MainPage.xaml?Category=" + category, UriKind.Relative);
// Otherwise perform normal launch.
One more step to ensure that your application will use your new UriMapper, go to App.xamls.cs file in the InitializePhoneApplication() method and add this line:
RootFrame.UriMapper = new AssociationUriMapper();
Your app will now try to detect if it was launched from the normal way or from the URI association, and in this case it will parse the parameters provided and redirect to the proper page.
How to retrieve the parameters once you have been redirected
Like for any page navigation in Windows Phone you'll have to check the QueryString in NavigationContext once you've reached your target page to retrieve your parameters:
protected override void OnNavigatedTo(NavigationEventArgs e)
Category = int.Parse(NavigationContext.QueryString["Category"]);
What will and will not work
What will trigger your URI association and launch your app:
- Get the URI from NFC tag.
- Get the URI by mail.
- Click on a HTML link containing the URI.
- Webpage redirection with a custom protocol.
- Get the URI from NFC device sharing an URI (e.g. PublishUriMessage(Uri) from ProximityDevice).
What will NOT trigger your URI association and launch your app
- Enter directly the URI in the Web Browser.
- Scan a QR code from Bing search.
What MAY trigger your URI association and launch your app
- Get the URI by SMS. It seems to depend on the uri your registered and could be connected to its length
What if many applications registered the same name
In this case the user will be prompted to select which application he want to launch
URI associations can also be used to provide a simple form of inter-app communication. Two apps that register URI associations could send each other messages in their respective URI association parameters (typically apps use URI parameters to choose what page or information to display, but their usage is completely app dependent and could be used for messaging). The code example shows how this can be done with two apps sending text and displaying it in each other's UI. Note that the launching process will request to install the other app is installed if it has not been.
For this to work correctly it is necessary that communicating apps share a common protocol. A more generalised approach might be to define a "standard" protocol for messaging, or for querying other apps about what messaging protocols they support (ie send them a message with "tell me your protocols" and parse the response"). This would allow arbitrary communications with apps that support a set of protocols.
Document your custom URI protocol
Your application can now be started by, and can receive data from, other applications. But in order for this to work, you must document your protocol. You add the scheme to the URI Association Schemes List to advertise it to other developers.
appcommunication.zip Code sample for section 'Inter-app communication'