In iOS, there are several built-in intercepts for launching application-oriented applications based on the passed URL, for example, for processing http: // (for Safari), processing addresses (for Google maps) and phone numbers (for the built-in phone application). In several applications, the standard practice of implementing a rarely used ability (for most applications) registers its own service prefix. Two useful applications that come to mind that implement this are facebook: // and skype: //, and this is a convenient way to add quasi-integration with their application to yours. Skype even does this on most desktop OSs, so you can literally run the skype: // 555-1234 command prompt. You can also check these registered service prefixes and show useful menu options in your applications, but I digress.
Like all of these service handlers, built-in or not, the problem with iOS is that you are losing the user, and their experience flow ends with the phone application (for example). Yes, you can embed web views to handle some cases, but things like the phone still benefit.
I suggest that it would be great if iOS applications passed a trailing URL as part of their arguments (even if they accept and can handle, say, two arguments), that by agreement, when our application is completed, we launch the trailing URL may have been optionally handed. If fully supported, this will allow the integration of multiple applications and the advanced user interface downstream. It seems to me that it is possible, for example, to start a phone call and return the user to my application when it is completed by running my application again using the URL that I passed to it, for example, "myapp: // return-context-values" . Obviously, this could be undertaken further.
Does such a mechanism already exist in some way? If not, I would like to hear your thoughts on this idea.
source share