As it came up in a thread (somewhere) and also for my OI Timesheet app, I wanted to see how difficult it is to use a different UI for the same data.
For Android apps, e.g. this is easily done, as I can tell my phone to use a different app for a particular URL (the redirect url).
For the web this is more difficult because blockstack.js enforces the same host for the app domain, the redirect url and the manifest url. Is this really necessary? Let’s say we have an alternative app that wants to catch the redirect. What if the redirect to the alternative app could be specified in the auth request and the blockstack browser would show the user something like:
“Select an ID (showing the icon from the manifest that is derived from the redirect url)
Alternative app for <> (showing icon from manifest)
<> (alternative domain) wants to use your data from <>(app domain) and read your basic info … . Select an ID to use:”
Is this too confusing for the user?
Especially, with the introduction of UserSessions and storage strategies in blockstack.js this could make sense to have apps that can use data from other apps, like a project managment app can read the data of a timesheet app (but not the other way round).
The user can be asked to sign in for certain actions and then sign out again.
This is different to data collections in the sense that this data is not general use case data like photos, phone book. It is
- to enable alternative apps and
- to enable collaboration between related apps without putting everything into one app/domain