"Open Links in Apps" option is obsolete
- Edited
Vlad I would say the app addresses a possible „missing feature“ of IOS, which is that if multiple apps listen for the same URL scheme, it opens just one of them without providing a choice. Opener gives them a choice, not by allowing different apps to listen to the same URL scheme as this would create chaos in other apps if they would do, but by transforming URLs to different apps URL schemes like to make it valuable for Twitter and Tweetbot which share a similar purpose. Both apps handle the same content but the URL scheme is different: twitter://… and tweetbot://…, however not knowing details, it makes sense for some power users to open a tweet once in the Twitter and another time in the Tweetbot app.
Which I don’t see a usecase for to be honest.
If Orion would just ask to open an URL with an external app, if the URL scheme is registered, I‘m more than happy.
You can even do it better than Safari which just asks yes or cancel and if you hit cancel it doesn’t do anything. I like your current user prompt because sometimes it makes sense to open links in the browser directly and sometimes it is only possible open it with other apps.
rosenrot This was a long thread and you seem to have a point.
I am going to ask you to list steps you would like Orion to undertake from its current state to this new state, making it a specification. Also power user case, which caused us having this feature built in the first place needs to be satisfied. Be as detailed as you can explaining UI/UX options along the way.
- Edited
Vlad So let me think...
This use case A combines the regular user and the power user in case there is a URL registered:
- Click on any link that has a registered URL scheme (as this indicates there is a dedicated app for this link).
- Orion pops up this user input; the user can select what he wants.
2a. Selecting if he wants his choice to be remembered.
2b. The app list holds first the registered app and follows the list of apps that can open such a link by link manipulation (e.g., change twitter:// to tweetbot:// - comes from the Orion-supported apps list).
2c. The Orion should show as a separate app that allows opening the link within the browser itself.
In case there is no registered URL scheme (use case B), but there is an app in the Orion-supported app list that would allow for link manipulation (e.g. twitter:// to tweetbot:// but twitter:// is not registered as the app is not installed):
- Follow use case A but don't show the Twitter app on top of the list.
On long press on a link, there should be "Open In" shown as an additional option (otherwise grayed out) to change the behavior if
- "Remember my Choice" was set previously as this allows you to change your preset.
- An app was installed that registered an URL scheme.
- Another app was listed on the Orion-supported apps list.
Additionally, universal links should be treated the same way as URL schemes. Universal links should lead to even better user experience and this is completely alright. However, it could become annoying to non-average users. This is where the above described UI/UX options are coming in. The user can freely decide if she/he would like to be a average user or not by simply selecting what she/he wants. The first app in the "Open In list" is mimicing the average user choice. Non-average users might be disturbed as universal links open external applications while in private browsing mode. We had this discussion over here: https://orionfeedback.org/d/3832-ask-user-to-open-link-in-associated-app-during-private-browsing/7
Here is more information about universal links:
It seems that universal links, the way service providers can tell which app can use their links, is exactly what the Orion-support app list is, just provided by the service providers themselves. The Orion-supported apps list adds freedom as the service providers prefer their apps to be used.
I would say that's it. I'm, of course, open to comments.
janpeeters Thank you for confirming that these mock-ups make sense. I'm entirely with you that it makes a difference compared to most other available browsers, especially on iOS.
Also, I believe this feature is not getting the attention it deserves right now as most users found their workarounds or think it can't be done as it isn't available in any other browser. Once it is implemented, it won't take long until other browsers mimic it.
Hello @rosenrot & @janpeeters,
I'm nano, Orion iOS engineer. I'm working on this feature and I wanted to confirm that I understand the general flow for this feature. I'm attaching a flow chart showing the possible paths the app can take when you either tap a link, or long-press a link to show the contextual menu. Please let me know if this is the expected behavior, and if not, where it should be different.
Additionally, @rosenrot, you mentioned not having this problem when using Brave. Would you mind sharing a test-case website that has links which show your desired behavior? It could help me see what the end-user experience could be. Thanks!
- Edited
nanoscrew Thanks for reaching out. Before going into details, let me quickly comment on the flow chart.
In general, it would be great if the user could decide if she/he wants to open links externally, independent if it is an url scheme, url built-in, or a universal link. I think the flow chart doesn't address that wish, does it? I would like to see the "Open in..." popup in any case, url scheme, app listed in built-in list of apps, universal links. From my perspective there is no need for the confirmation alert.
What alerts me is your note. For me, this means that we can't rely on the registered url schemes. In case I would click on 50 (different) links not being https/http the Orion browser would from that moment on always get a "No" for new urls. So both cases "tap link" and long-press link" would return "No" at the first branch. Am I correct?
If I'm correct and having in mind that Apple suggests moving from url schemes to universal links, we might go in a slightly different direction - completely ignoring url schemes. I would be happy to hear your thoughts nanoscrew janpeeters .
rosenrot Happy holidays and thanks for the reply! Responding, in the order you wrote:
- My flow chart may not have conveyed this, but your goal of asking the user whether they want to open an external link in another app is exactly the goal in my chart. For any link that could be opened in another app, the "Open in…" popup should appear (unless you've selected to "Remember by choice" as shown in your screenshot above, in which case we'd immediately attempt to open in your preferred app).
- You're right to be concerned about the scheme-detection limitations in iOS 15+. That said, it's ultimately a UX choice whether to attempt opening in another app. Worst case is we can't tell whether the app is installed, but the user wishes to try opening it in another app, and we show an error message that "App <X> is not installed". Not a seamless experience, but not destructive either.
I'll continue working on this, and we'll update this thread once it's available.
-nano
Implementing a way of opening app specific links, when a link is supposed to open an app.
Right now Safari is capable of doing this but Orion displays an error. This happens mostly with Banking apps and App Store links.
The links always start with “<appname>://“, for example chip://
Steps to reproduce:
- Search for an app that you have installed
- Tap the link for the app on App Store
- When the Dialog appears, tap “Open in Browser”
Expected behavior:
To open the website in browser.
Orion, OS version; hardware type:
Orion 1.2.4; iOS 16.0; iPhone 13;
Image/Video**:
**
Thanks @rosenrot and @nanoscrew I’m happy to see this is in the next release. Sorry to say that I didn’t see any notifications of your mentions otherwise I would have chipped in. Best!
I wanted to also report that some apps might not register the links properly, so it would be nice (if possible) to allow setting a "custom app", so when some apps don't register their links properly we can always override which app should handle some deeplinks.
In particular, I wasn't able to open a Clash of Clans base layout link with Orion. I was able to say "open in app" but Orion would error saying "opening the deep link clashofclans://... requires an app that can handle "clashofclans" scheme to be installed on this device", and I do have the app installed...