User interface to allow opening in another app? (Open-with functionality)

[josephguillaume]

SolidOS using the data browser hack is in a privileged position where its registered panes are the default view when navigating to a resource.
Even if dynamic panes become possible (SolidOS/pane-registry#28), this provides an inward-focused experience rather than encouraging interaction with a broader ecosystem of specialised apps.

It turns out that in the context of SAI and the principle of least privilege, there is also the opportunity for SolidOS to act as a bridge to enable follow your nose between apps.
solid/data-interoperability-panel#325

I'm opening this issue to discuss what user interface SolidOS should provide to help the user open a resource in another app.

As test cases, one could consider offering to open:

• Dokieli as a standalone app rather than as a pane
• recipes in Umai
• Resources or containers in Solid File Manager, Solid Content Manager, Penny or PodOS
• ...

[josephguillaume]

A minimal implementation could provide an additional pane with links that open the resource in other apps.

The same pane could allow managing a set of external app registries to draw from, and managing preferred apps.

The pane would be visible for all resources. It would therefore be very prominent and may not provide the best user experience.

Looking forward to SAI support, the pane could also manage trusted application settings related to the specific resource, in the same way that if SolidOS ended up acting as an authorisation agent, it would grant access to each specific app prior to being able to open a link.
The pane could therefore be seen as a resource-specific app management pane.

[josephguillaume]

Here's a mock-up using ionic components:

• A list of apps, as buttons that will open the resource in the respective app
• An alert icon if the app has not yet been authorised/trusted. This could be connected to a modal
• A list of app registries in preference order, reorderable
• App registries can be added (with a modal) and deleted (with a swipe interaction)

I assume adding a dependency on ionic is not desirable, but if the general UI/UX is suitable as a pane, then the next step would be to make it operational, and then the CSS+interactions could be reimplemented later.