[clarencemartin]

Allows APPLI to launch a URL to their respective applications. It opens the default applications based on the custom URL schemes.
Is there a list of any other URL schemes? There are a few URL schemes listed in the documents. 

[marktalluto]

Hello Clarence,

The launch URL action comes with support for the following:
http: and https: URLs, which launch in the default browser application if available
file: URLs, which open the file in the associated application
tel: URLs, which open the dialer with a given phone number

Some other uses:
On macOS you can open the system preferences and jump to the Privacy tab.
launch url "x-apple.systempreferences:com.apple.preference.security?Privacy_Automation"

On mobile you can send an SMS:
launch url("sms:" & tMobile & "?body=" & tMessage)

Launching URLs on a mobile device will take the user to another app.

[clarencemartin]

Can these launch URLs be added as a list in the documentation?
They are kind of there, but not as a specific list.
Sorry if this seems picky.

[marktalluto]

That is a good idea. I'll add them now. You will see them on Wed's push.

[agarzia]

Just a heads up that there is no master list of URL schemas. Any installed application can register a bunch of them and the OS comes with some of its own. We'll post the most popular ones, but there is no way to create an exhaustive list. Developers in the Apple ecosystem, specially those shipping mobile apps, kinda coalesced around a spec of their own called x-callback. You can learn more about it on:

https://x-callback-url.com/

Many iOS/iPadOS/macOS apps support these URLs.

The most common schemas are:

• "http" and "https" for websites.
  
• "sms" for opening the messaging app.
  
• "mailto" for opening the email client.
  
• "tel" for opening the phone dialer.
  

A non-exhaustive list of schemes can be seen on https://en.wikipedia.org/wiki/List_of_URI_schemes

The objective of those URL schemes is to open another application. Such schemes can't be used to initiate a call or send an email, all they do is open another app with maybe the information pre-filled. Accepting URL arguments and so on is at the discretion of the opening app, there are no guarantees.

Also, there is no way to verify if the chosen URL can be opened. Launching a third-party app scheme such as `x-notion` or `things` will fail if those apps are not installed and there is no way for your app to know. Because of that it is better to offer launching such URLs as an additional feature at the user discretion or when you're sure the user has an application to handle the scheme.

[clarencemartin]

Thanks, Andre. I'll explore the links posted.