"The best way to solve this problem is to eliminate the need for hacky bookmarklets entirely: Add a proper registry of apps that can accept URLs from Safari"
I disagree that this is the best way to solve the problem: it would restrict availability of integration with Safari to native apps, leaving pure web-hosted apps at a disadvantage. Why should every web-hosted app that handles URLs have to produce an iPhone app just to lower the user-experience hurdle? And bear in mind that the app won't have access to cookies set in Safari, so the user will need to authenticate themselves twice - once in Safari, once in the app.
I think the best solution would be one completely within Safari - window.external.AddFavorite or something similar.
> I think the best solution would be one completely within Safari - window.external.AddFavorite or something similar.
But then, what of native applications? And what if you actually just want to send a URL to an other native application? Also, AddFavorite (terrific casing from the MSIE team here) with arbitrary JS?
Also, if the registry/send to method works with offline web applications, then there is no restriction, the site "just" need to bundle a small offline webapp able to handle the information (not sure if there is any specified way for the OS/shell to send data to offline web applications though)
I disagree that this is the best way to solve the problem: it would restrict availability of integration with Safari to native apps, leaving pure web-hosted apps at a disadvantage. Why should every web-hosted app that handles URLs have to produce an iPhone app just to lower the user-experience hurdle? And bear in mind that the app won't have access to cookies set in Safari, so the user will need to authenticate themselves twice - once in Safari, once in the app.
I think the best solution would be one completely within Safari - window.external.AddFavorite or something similar.