Build and deploy an app

Deploying an Agentic Development Toolkit (ADT) Web Viewer app means bundling the web app into a single HTML file and storing it inside the FileMaker file so a Web Viewer layout can load it. There's no external host to stand up — the built artifact lives in the FileMaker file itself. See How Embedded Deployment Works for how that storage works and what other deployment shapes exist.

Deploy the app

  1. Run checks. Ask your coding agent to run the available type, lint, and production-build checks.

  2. Build the app. The production build produces one self-contained HTML file for FileMaker.

  3. Deploy to FileMaker. Ask the agent to place that build in the intended connected file. If several files are connected, name the target explicitly.

  4. Verify inside FileMaker. Navigate to the Web Viewer layout and confirm the deployed app loads with real data.

Warning  Deploying writes into the connected file Deploying writes the bundled app directly into the connected FileMaker file. Only run it against the file you mean to update. If users are connected to a production file, they may see the change immediately, so prefer a development file or a controlled deployment window.

End-user requirements

Users do not need the ADT application installed to open the Web Viewer app. The app's HTML and JavaScript are stored in the FileMaker file and rendered by FileMaker's Web Viewer. However, an app may depend on ADT scripts or custom functions installed in that file; keep those components for as long as the app uses them.