Launcher API

[adamfisher]

Description of the Feature

Provide the ability to detect and launch another application already installed on the device.

//Updated by JM

API Declaration

Integration Point: Launcher

API:

- Task<bool> CanOpenAsync(string uri);
- Task<bool> CanOpenAsync(Uri uri);
- Task OpenAsync(string uri);
- Task OpenAsync(Uri uri);

Implementations:

CanOpenAsync:

• UWP: QueryUriSupportAsync - https://docs.microsoft.com/en-us/uwp/api/windows.system.launcher.queryurisupportasync
• Android: QueryIntentActivities
• iOS: UIApplication.SharedApplication.CanOpenUrl

OpenAsync:

• UWP: Launcher LaunchUriAsync
• Android: Standard launcher stuff
• iOS: UIApplication.SharedApplication.OpenURL

Documentation links for supported platforms

• iOS Inter-App Communication
• Android: Sending the User to Another App
• UWP: Launch an app with a URI

[adamfisher]

I realize there is some overlap with the way the Browser API works due to it handling HTTP protocols so this proposal could morph into enhancing it to support launching other applications. iOS specifically appears to be using the same code that would open another application when using BrowserLaunchType.External.

Changing the Browser API to Launcher API seems like a more appropriate generic/high-level thing since launching the device browser is only one such app. What do you guys think?

[jamesmontemagno]

I am pretty open to changing the name here to Launcher instead of Browser as this should work out of the box with our current implementation. New check I think is good for this instance as well. Will triage Monday.

[jamesmontemagno]

The question to me will be is it alright to have our single API for opening uri.. or perhaps just a new API that is always extrenal. Leaning that way.

[mattleibow]

Yeah, we want the ability for the browser to be more specialized. It needs to support Chorme/Safari views.

I am not such a fan of merging the two concepts.

[jamesmontemagno]

Agreed it should be in the "Launcher" name.

I will be updating the main comment now with discussion points.

[Redth]

On Android we should essentially use QueryIntentActivities to see if there are any activities available to match our intent (which likely is just created with ACTION_VIEW).

[jamesmontemagno]

The only question i have is if we need the application id at all or just the uri is fine.

The only thing would be to launch a specific app if there are multiple that supports the scheme... not sure if that is supported on all platforms (assumption is no).

[Redth]

I think taking the app id into consideration makes things considerably more challenging or impossible on some platforms (eg: iOS).

In practice I think most apps declare their own unique uri scheme anyway.

[jamesmontemagno]

yeah, i would leave it off for now in first iteration.