The Blue Jetty Manifesto

Imagine someone asking an AI assistant for an app to help them train for their first marathon. A publisher has built a beginner plan that fits around a working week, with a useful place to start. An answer that explains that experience and links to it can become an entrance to the app.

Yet much of what makes a mobile app useful lives inside the app. AI assistants researching it often encounter fragments: a store description, a marketing page, a release note. The specific experiences, the needs they serve, and the paths into them can remain difficult to see.

Publishers should have a direct way to make that knowledge available. AI Mobile Context (AMC) is publisher-authorized context that tells AI assistants what an app does, when it is relevant, and where to send the user next.

AMC is the context. Blue Jetty is infrastructure for publishing, maintaining, and delivering it. That distinction matters: the publisher's knowledge of its app should remain useful as AI systems, distribution channels, and service providers change.

An answer becomes an entrance

An assistant can bring discovery, evaluation, recommendation, and handoff together in one interaction. Someone describes a goal or a constraint. The answer can explain which app fits, why a particular experience matters, and how to get started.

For a mobile team, that introduction is part of the product experience. A running tracker and a beginner marathon plan may live in the same app, but they answer different needs. The publisher has already done the work to build the experience. The next challenge is making its relevance visible outside the app.

Specific context gives an assistant more to work with: who the plan suits, what it includes, and which destination the publisher has provided. When an answer becomes an entrance, app context becomes part of the acquisition experience itself.

GEO creates an opportunity for richer app context

Generative Engine Optimization helps publishers make their public content discoverable and useful in AI-generated answers. Clear pages, helpful FAQs, accessible content, and credible explanations all contribute to that work. Google's guidance for AI features in Search keeps familiar SEO fundamentals central, including crawl access, findable content, and structured data that matches the page.

AMC complements that work by making the app's details explicit and connected. A page can explain that an app helps runners. An app map can connect a beginner's goal to a training experience, its relevant constraints, an available offer, and a publisher-preferred destination.

A good website and a useful FAQ remain valuable. As an app grows, however, expressing every relationship between capabilities, experiences, conditions, platforms, and links through separate questions becomes cumbersome. Publishers deserve a maintainable way to supply that detail alongside their public explanations.

Mobile apps need an explicit map

The public web gives a crawler pages and links to follow. An app's useful structure may instead sit behind navigation, sign-in, filters, or an installed experience. The team building it knows how those pieces fit together. An assistant researching it needs an accessible account of that structure.

An app map can connect:

• What the app does and which needs it serves.
• The experiences and selected content that make it useful.
• Relevant conditions, platform differences, and available offers.
• The publisher's preferred destinations for getting started.
• Who supplied the context and when it was updated.

These relationships are the reason to make AMC structured and machine-readable. A description can sit beside the exact experience it describes. An offer can carry its own conditions and expiry. A destination can identify the platform and situation it supports. The consuming system has less relationship-building to do from disconnected fragments.

Natural language still does essential work inside that structure. It explains a feature, a use case, or a meaningful distinction. Explicit fields give those explanations scope and connect them to the right next step. The value comes from the information and its relationships, not from putting ordinary marketing copy inside JSON.

Publishers can start with the major capabilities and experiences, then add selected detail where it helps someone choose. The interactive tools, private records, live services, and full product experience remain inside the app. A useful map makes that experience easier to understand and reach.

The next step belongs with the context

Mobile teams invest in app links, new-user journeys, and attribution because arrival matters. AMC should carry that investment forward. The explanation of an experience and the route into it belong together.

In the marathon example, the publisher can describe the beginner plan and supply its approved training-plan link. The existing link provider and app implementation handle the appropriate installed-user or new-user path. A relevant offer can accompany the link when the publisher has supplied its conditions.

Blue Jetty makes app context available to AI assistants, which decide whether and how to use it for the user's request. The publisher's existing MMP measures eligible downstream activity when users follow its links. Packet requests show retrieval; they are a separate observation from recommendations, clicks, or installations.

Publisher control and independent judgment belong together

Publishers control the context and preferred destinations they authorize for their own apps. They should review its accuracy, rights, and public exposure before publication. An assistant's judgment remains independent: it decides what is relevant to the person asking.

Blue Jetty makes provenance explicit, distinguishing publisher-supplied information from separately observed evidence. That gives readers a clear account of where the information came from. The protocol documentation carries the detailed rules; the principle is simple enough to apply throughout the product.

App context should stay current and portable

AMC belongs to the publisher. Its product facts should travel across AI systems and the mobile stack without being rewritten for every vendor. Platform-specific experiences and links can differ while the app retains a coherent identity.

Keeping that context current is an ongoing publishing responsibility. Features change, destinations move, and offers expire. Publishers need to update, correct, and withdraw information with the same care they give its first publication. Retrieval paths can differ too, so the same authorized context should be available through multiple discoverable surfaces.

Portability and maintenance work together. A team should be able to change agencies, link providers, or AI priorities while retaining control of what its app says about itself.

Why we are building Blue Jetty

Blue Jetty is a mobile context engine (MCE) for AI search. It helps AI assistants discover mobile apps, understand the experiences they offer, and connect users through publisher-preferred links. The engine brings the app index, publisher-authorized context, update history, preferred destinations, and visibility into crawler requests into one publishing workflow.

Blue Jetty also maintains a public app index that helps AI assistants find and identify apps across stores. Source-attributed records provide a starting point for research. Publisher-authorized AMC adds the team’s account of relevant experiences, conditions and preferred destinations. The index keeps those sources distinct so assistants can understand who supplied each kind of information.

Developers and coding agents can prepare the context using knowledge already present in the app and its implementation. Product and growth teams can review the experiences, offers, and destinations they want potential users to understand. The authorized publisher decides what becomes public.

We want that work to become straightforward enough to be an ordinary part of shipping an app. A small team should be able to give AI assistants a useful account of its product without maintaining a separate explanation for every system that might retrieve it.

AI Mobile Context belongs in the publisher's toolkit

Mobile publishers already manage their store presence, website, links, and attribution. We believe AI Mobile Context belongs alongside them: an explicit, current, publisher-authorized account of what the app offers and where its value can be experienced.

The future we are building toward is one where teams routinely ask: Who owns our AMC? Does it reflect the app we ship today? Can AI assistants find and use it?

When an answer can become an entrance to your app, the context behind that answer deserves the same care as the app itself.