Mobile App Link Functionality – Spire
Issue / Request:
We need mobile links to open directly in the Moblico app when the app is installed. If the app is not installed, the link should fall back to Safari and provide the user with an option to download the app.
Moblico has already completed their portion of the work required to support this functionality, so there has already been development and investment on our side.
We have been advised that this functionality is supported with Classic but is not currently supported with Spire. This is a significant concern since Classic is no longer supported. Functionality that is supported in Classic should be available in Spire.
This also does not appear to be new or experimental functionality. Apple and Google have supported their respective app-linking approaches for many years, and the underlying /.well-known/ convention has been standardized for quite some time.
Expected Functionality
We are requesting that Spire support mobile app links with the following behavior:
If the Moblico app is installed: Open the link directly in the app.
If the Moblico app is not installed: Open the link in Safari and provide the user with an option to download the app.
Request
Please provide a supported solution for this functionality in Spire. Since this capability exists in Classic, we would expect equivalent functionality to be available in Spire, particularly as Classic is being retired.
We would also appreciate information on the expected timeline/release for supporting this functionality in Spire.
Great news! Our team has added support for .well-known file hosting; it was included in September-sts release - 5.2.2609.386+sts.
Self-service .well-known file hosting – Launch third-party tools, mobile apps, and domain verifications immediately by removing developer sprint dependencies and production release cycles. Implementers can upload app-site association, domain verification, and mobile link verification files directly to/userfiles/_system/.well-known, and Spire serves them at /.well-known/<filename> allowing critical integrations to go live without waiting for custom code deployments or scheduled releases. See Media library.