Content
View differences
Updated by Marc Alcobé about 1 year ago
**ON HOLD: Requires web app work on API**
<br>
**As** a mobile user
**I want to** see a WorkPackage in the mobile app when I click a link in my email on mobile
**Problem:** We have to specify each subdomain separately in the app which hardly possible to achieve. also we can't specify on-premice domains.
**Available options**
* use url schema instead of http link.
in this case we don't have to rely on domain names. Also we are able to configure links as we need:
i.e.: `openproject://workpackage/12345`
or `openproject://notifications`
* use redirect links. So we will stick always to one domain and then redirect to a correct instance or to the app
i.e.: [`https://openproject.com/deep-linking?instance:custom-domain;content:workpackage/12345`](https://openproject.com/deep-linking?instance:custom-domain;content:workpackage/12345)
* wild option (most likely useless) - predefine a huge list of possible associated domains in the app.
* maybe inside the email we can add a separate button "see in the app" that will have a dedicated url?
<br>
**As** a mobile user
**I want to** see a WorkPackage in the mobile app when I click a link in my email on mobile
**Problem:** We have to specify each subdomain separately in the app which hardly possible to achieve. also we can't specify on-premice domains.
**Available options**
* use url schema instead of http link.
in this case we don't have to rely on domain names. Also we are able to configure links as we need:
i.e.: `openproject://workpackage/12345`
or `openproject://notifications`
i.e.: [`https://openproject.com/deep-linking?instance:custom-domain;content:workpackage/12345`](https://openproject.com/deep-linking?instance:custom-domain;content:workpackage/12345)