Can a single domain direct the user to different app clips depending on what page the user is on?
Scenario:
portfolio.com/OrrangesApp
portfolio.com/BananasApp
Each of these pages can have separate <meta> tags for displaying different banners for different Apps/AppClips. That part makes sense to me.
I'm curious how this would look in the AASA file.
The file must state:
How do I direct the OS to a different clip based on a different URL path?
Is that fulfilled through the the AppStoreConnect configuration? I was under the impression we had to match the URL with the AASA, but I'm suspecting that only applies to the domain?
Am I on the right track, here?
Scenario:
portfolio.com/OrrangesApp
portfolio.com/BananasApp
Each of these pages can have separate <meta> tags for displaying different banners for different Apps/AppClips. That part makes sense to me.
I'm curious how this would look in the AASA file.
The file must state:
Code Block "appclips": { "apps": ["ABCED12345.com.example.OrangesApp", "ABCED12345.com.example.BananasApp"] }
How do I direct the OS to a different clip based on a different URL path?
Is that fulfilled through the the AppStoreConnect configuration? I was under the impression we had to match the URL with the AASA, but I'm suspecting that only applies to the domain?
Am I on the right track, here?
The system used for app clips is different than universal links. Both use the associated domains entitlement and Apple App Site Associations (AASA) file to prove associations. However, with universal links you would set up URL pattern matches on your server using your AASA, while with app clips you register URL prefix matches as separate advanced app clip experiences using App Store Connect.
The configure and link your app clips session goes into detail on this. For the example you gave:
Because you're working with two separate app clips, you don't need to set up an advanced experience. On each page, you'll have a <meta name="apple-itunes-app" content="app-id=myAppStoreID, app-clip-bundle-id=appClipBundleID"> tag. Since each page targets a different app clip, you'd set myAppStoreID and appClipBundleID to the appropriate pair. Assuming that your domain and app's association is validated, Safari will display the smart app banner, allowing you to launch the clip.
(Note: some of this may be hard to test without submitting a build of your app which includes your clip, because the required associations cannot be validated until this is done).
I would still suggest showing some fallback content. App clips are a new feature to iOS 14, and if you may get visits from people on older versions of iOS.
The configure and link your app clips session goes into detail on this. For the example you gave:
Your AASA file looks correct. You want to your domain (portfolio.org) to be associated with both app clip's identifiers. Be sure that in each app clip you'd then add the associated domains entitlement with appclip:portfolio.com.Scenario:
portfolio.com/OrrangesApp
portfolio.com/BananasApp
Each of these pages can have separate <meta> tags for displaying different banners for different Apps/AppClips. That part makes sense to me.
Because you're working with two separate app clips, you don't need to set up an advanced experience. On each page, you'll have a <meta name="apple-itunes-app" content="app-id=myAppStoreID, app-clip-bundle-id=appClipBundleID"> tag. Since each page targets a different app clip, you'd set myAppStoreID and appClipBundleID to the appropriate pair. Assuming that your domain and app's association is validated, Safari will display the smart app banner, allowing you to launch the clip.
(Note: some of this may be hard to test without submitting a build of your app which includes your clip, because the required associations cannot be validated until this is done).
If you expect this page to be navigated to in Safari, you'll need to display something because we will not show the app clip card on navigation. The user has to see and interact with the banner UI, which is only shown on pages with the appropriate <meta> tag from above. For invocation from visual codes or NFC tags, you could encode a URL which doesn't exist on your server, because those methods will go straight to the app clip card.Also, lets say I do us "portfolio.com/OrrangesApp/Clip" Does this have to resolve to an actual web page? If nothing existed on the web server at that location would it direct iOS14 users to the app clip, and other users to a 404?
I would still suggest showing some fallback content. App clips are a new feature to iOS 14, and if you may get visits from people on older versions of iOS.
