This page covers example prompts for the Deploy applications use case. In this use case, you are approaching release of an ArcGIS application and want to make sure the app operates reliably in production. Ask prompts help clarify requirements such as licensing and readiness, while Plan prompts help prepare deployment, testing, and operations steps. See Types of prompts for how those prompt roles work together.
Prerequisites
- Connect to the MCP server and install the agent skills by following the Install and set up instructions.
- Start a new chat session in an existing application workspace.
- Run this prompt to set the session state:
Prompt
For my questions in this session, use the relevant installed Esri developer agent skills and MCP server to search current official Esri developer documentation. Keep answers concise and link to sources.Examples
Use these prompts as starting points for deployment and production-readiness tasks.
Prepare an app for production
Prompt
I have a mapping app for the web built with OpenLayers and I want to prepare it for production. Review this app for production readiness. Propose prioritized actions for performance, reliability, security, and attribution, with testable acceptance criteria and verification steps. Flag any gaps. Ask clarifying questions if needed and wait for approval before editing.The agent should:
- Check the application code, authentication setup, and ArcGIS product used.
- Recommend checks for performance, reliability, and secure ArcGIS services access.
- Identify considerations such as terms of use, error handling, and Esri and data attribution.
- Link to supporting ArcGIS documentation for further exploration.
Follow-up prompts:
What are the attribution requirements when using a public feature layer in my app?Apply the performance optimization recommendations to my app.
Plan offline field use
Prompt
I am preparing this ArcGIS mobile app for fieldwork without reliable connectivity. Plan offline field use for the app for [viewing maps, collecting data, or editing]. Check service, licensing, and sync requirements. Define testable acceptance criteria and verification steps. Flag gaps and wait for approval before editing.The agent should:
- Check whether the app’s maps and data support offline use.
- Recommend a workflow and note key service, licensing, and sync requirements.
- Link to ArcGIS documentation, suggest offline tests, and wait for approval before editing.
Follow-up prompts:
Can field users edit features offline and sync their changes later?What should I check if an offline map area fails to download or synchronize?
Prepare a mobile app for release
Prompt
I have an ArcGIS mobile app and I want to plan release of it for [iOS or Android] using [SDK]. Review signing, credential security, permissions, testing, licensing, and distribution; define testable release criteria and verification steps. Flag gaps and wait for approval before editing or submitting.The agent should:
- Review the project and outline steps for signing, secure credentials, permissions, testing, licensing, and distribution.
- Link to current ArcGIS documentation and note assumptions.
- Wait for approval before editing or submitting the app.
Follow-up prompts:
What are the steps to properly sign and distribute my ArcGIS mobile app?How can I test my ArcGIS mobile app on different devices and OS versions before release?
Determine licensing requirements for deployment
Prompt
I have an app that uses [ArcGIS Maps SDK and version] and requires [viewing maps, offline use, editing, or analysis capabilities]. Identify production licensing and extensions. Ask about missing details, then outline runtime configuration and release-build verification. Present the analysis for review. Do not change files.The agent should:
- Identify the SDK, version, and capabilities that affect licensing.
- Explain the required runtime license level and any extensions, distinguishing them from account or service-access requirements.
- Describe how to configure and verify licensing in a release build.
- Link to current official ArcGIS documentation and flag unresolved requirements.
Follow-up prompts:
How can I verify that the release build is licensed correctly on a clean device?Does the licensing approach support users who need to work offline?
Review Terms of Use considerations
Prompt
Review this app against applicable current Esri terms: https://developers.arcgis.com/documentation/terms-of-use/. Link relevant clauses and flag issues, assumptions, and missing details without inferring legal approval. If correction is needed, propose steps and verification for review. Do not edit files.The agent should:
- Find the Esri terms that apply and link to them.
- Check for potential issues with licensing, attribution, storage, or sharing.
- Note assumptions and missing information.
- Summarize findings without claiming legal approval.
Follow-up prompts:
Which Esri terms apply to the data and services my app uses?What should I change to address this concern?What information do you need to check this more accurately?