AI Mobile Context
Swell Atlas: From an AI Question to an App Handoff
See a synthetic app move from developer configuration to AI selection, attributed handoff, and a curated in-app destination.
Synthetic end-to-end example
A surf question becomes a publisher-approved app handoff.
The publisher website points the assistant to Blue Jetty. The app map connects a relevant experience to the publisher’s preferred link.
A developer publishes the app map, verifies the publisher and adds a website reference to Blue Jetty. This enriched example includes twenty selected records.
The question describes an intent. The packet supplies an explicit mapping to a relevant in-app item.
Following the website reference, it can retrieve Pelican Sands, explain the fit and recommend the publisher’s preferred link.
The selected URL requests the installed-app experience. Depending on configuration, the provider may handle store, attribution and deferred arrival.
View the historical test’s illustrative handoff fields
Selected fields for explanation; see the technical guide for the submission format.
{
"entity": "Pelican Sands",
"selection": {
"skillLevel": "beginner",
"breakType": "beach_break"
},
"publisherInstructions":
"Explain why it fits, then use our preferred link.",
"currentPromotion":
"New members save 20% on the first year.",
"recommended": {
"operator": "appsflyer",
"consumer": "chatgpt",
"verificationState": "declared"
}
}App experiences, relevant details, freshness, publisher preferences, an offer and approved links.
Live conditions, complete forecasts, proprietary guidance, accounts, commerce, fulfillment, and the ongoing product experience.
A potential user asks an AI assistant, “What app can help a beginner find a mellow surf spot?” Your team wants the answer to explain the relevant experience, include an appropriate offer, and send the person through the link you already use for deep linking and attribution.
This walkthrough uses fictional Swell Atlas to show where Blue Jetty fits. The app, screens, data, offers and destinations are illustrative. The useful pattern is the connection between your publisher website, the app context hosted by Blue Jetty, and your existing app links.
1. Your team publishes the app context
The growth team chooses what to explain: who the app helps, the experiences that fit common questions, any current offer, and the preferred link for each destination.
A developer or coding agent submits that app map through Blue Jetty's API. They complete publisher authorization and add the generated reference to the official website, including its llms.txt. Blue Jetty hosts and maintains the app context behind that reference.
The compact before/after example starts with a beginner spot-finder experience. The earlier enriched example pictured here adds twenty selected records: eight surf spots, four training sessions, five guides and forecasts, and three events. Those records demonstrate optional detail; the app's complete spot database stays in its own systems.
2. An assistant researches the user's question
The assistant can visit the publisher's pages while researching relevant apps. Those pages point to the Blue Jetty app map, where the assistant can retrieve more specific context.
In the enriched example, Pelican Sands is described as a beginner-oriented beach break with useful access and facility information. That helps the assistant explain why Swell Atlas could be worth trying for this question. The app delivers the complete guide, current conditions and interactive planning tools.
The website reference is the connection your team installs in this flow. Blue Jetty also provides lookup and search as additional ways to retrieve app context.
3. The answer includes a relevant experience and preferred link
The app map brings together the experience description, publisher instructions, active promotion and approved destination. Your team can request an MMP-first handoff and assign different links to different experiences.
An illustrative answer could say:
Swell Atlas includes beginner-oriented spot guides with access and facility details. Explore Pelican Sands in the app to see the complete guide and current conditions.
The action accompanying that answer can use the publisher's AppsFlyer OneLink. An active offer can appear alongside it when it fits the recommendation. Blue Jetty supplies the context and link preference; the assistant decides how to answer the person's question.
4. Your existing provider handles the click
The user follows the recommended link. With the appropriate configuration, the provider can open the linked experience for an installed user or route a new user to the store. AppsFlyer's OneLink guide covers those responsibilities.
Your app and link provider also determine deferred arrival after installation and which downstream events can be attributed. Native app opening relies on the app's existing platform setup, including mechanisms such as Android App Links. Test installed and new-user paths before publishing a destination.
What your team can inspect afterward
Blue Jetty shows recorded access to the app map. Your MMP and app analytics provide the downstream measurement available under your configuration and privacy settings. Keep those observations separate when evaluating the journey.
The technical case study contains the selected-record example and its sample-isolation controls. Swell Atlas remains private test data; this public walkthrough explains the flow so a real publisher can configure its own app.