• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Handling http:// URLs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handling http:// URLs


  • Subject: Re: Handling http:// URLs
  • From: Rick Mann <email@hidden>
  • Date: Tue, 13 Oct 2015 19:43:08 -0700

> On Oct 13, 2015, at 19:05 , Conrad Shultz <email@hidden> wrote:
>
>
>> On Oct 13, 2015, at 5:34 PM, Rick Mann <email@hidden> wrote:
>>
>>> On Oct 13, 2015, at 17:29 , Stephen J. Butler <email@hidden> wrote:
>>>
>>> I think you're talking about Seamless Linking/Universal Links. Introduced in iOS 9
>>>
>>> https://developer.apple.com/videos/play/wwdc2015-509/
>>>
>>> https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.html
>>
>> Yes, that's it, thank you. Sadly, it's not as cool as I had hoped (I really want, as a user, to be able to have multiple choices when tapping certain kinds of URL, but that's for another day). This will address our current needs.
>
> As always, if there are enhancements you’d like to see, please file a bug at https://bugreport.apple.com.

I've filed this request periodically for years.

> That said, could you elaborate on what you mean by "multiple choices when tapping certain kinds of URL”? Universal links are based on mutual trust: an app and website mutually agree to let one another handle links. You can have different apps handle different parts of your website (e.g. a video player to handle videos you host and a social app to handle messaging through your site).

Admittedly, I'm currently struggling to find a concrete example of why this is useful, but I just know it is:

Any app(s) should be able to register URL patterns they're able to handle. If the user takes an action that results in a URL being requested that one or more of these apps could handle, iOS should present the user with a list of these URLs, and get the user's permission to then handle the URL.

The user should be able to do several things:

- Choose the app to handle the URL
- Make that choice permanent (and skip the choice) for that particular pattern
- Permanently bar an app from being considered
- Order the apps per pattern

- Read an NFC tag that encodes a URL, and present the same dialog

- Finally: allow iOS apps to modify the Wi-Fi settings (with user permission first).

This is my ideal world scenario. I realize the last two aren't strictly about apps handling URLs, although a compelling argument could be made that doing so opens a whole new world of applications.

I've written several RADAR requests covering all of this.


--
Rick Mann
email@hidden



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Handling http:// URLs (From: Rick Mann <email@hidden>)
 >Re: Handling http:// URLs (From: "Stephen J. Butler" <email@hidden>)
 >Re: Handling http:// URLs (From: Rick Mann <email@hidden>)
 >Re: Handling http:// URLs (From: Conrad Shultz <email@hidden>)

  • Prev by Date: More Xcode 7 inconsistency?
  • Next by Date: Re: More Xcode 7 inconsistency?
  • Previous by thread: Re: Handling http:// URLs
  • Next by thread: Re: Handling http:// URLs
  • Index(es):
    • Date
    • Thread