camp.forestexplorer.org/checkin/413/sites/7
In the above URL, I saw that metadata can be tied to anything starting with camp.forestexplorer.org/checkin/413. Does the rest of the url (/sites/7) still get passed onto the app clip? Is the App Clip initialized with the url in some way?
For example, if the user opens the app clip with this url and the application needs to show different images for site 7 and site 8 or if the user needs to check into the specific site, how is that information passed on? Is this use-case possible?
In the above URL, I saw that metadata can be tied to anything starting with camp.forestexplorer.org/checkin/413. Does the rest of the url (/sites/7) still get passed onto the app clip? Is the App Clip initialized with the url in some way?
For example, if the user opens the app clip with this url and the application needs to show different images for site 7 and site 8 or if the user needs to check into the specific site, how is that information passed on? Is this use-case possible?
Hi there,
Yes, what you describe is possible. You'd set up the app clip experience such that you register a generic URL, for example yourdomain.com. When a user invokes the app clip, for example from an NFC tag, you could encode info in the URL, for example, yourdomain.com/thing/otherthing/1234, and when the user allows the app clip to launch in the app clip card, you'd get the whole URL on launch.
The session Configure and Link Your App Clips goes into more detail. The developer docs also describes this in Configuring Your App Clip's Launch Experience and Responding to Invocations.
Yes, what you describe is possible. You'd set up the app clip experience such that you register a generic URL, for example yourdomain.com. When a user invokes the app clip, for example from an NFC tag, you could encode info in the URL, for example, yourdomain.com/thing/otherthing/1234, and when the user allows the app clip to launch in the app clip card, you'd get the whole URL on launch.
The session Configure and Link Your App Clips goes into more detail. The developer docs also describes this in Configuring Your App Clip's Launch Experience and Responding to Invocations.
