migrate-googleai

To migrate a Google AI Studio app to a static Domo deployment, you transition the project from server-based hosting to client-side static hosting by validating build pipelines, adjusting subpath routing, and using the domo publish workflow to deploy the dist/ directory.

HashRouter is required when moving to the Domo App Platform because static Domo deployments use subpath hosting, and HashRouter ensures routing resilience behind non-root URLs without server-side routing configuration.

When migrating to Domo static deployments, you normalize environment variables for browser-based apps and avoid client-side secrets, ensuring safe handling of configuration during the static hosting transition.

Domo App Platform static deployments require build pipeline validation that enforces production-ready artifacts in the dist/ directory, relative asset paths, and a postbuild copy for the manifest if needed.

No, Google AI Studio projects are server-based and must be converted into a Domo App Platform static deployment contract, which involves adjusting routing, packaging artifacts under dist/, and running the domo publish workflow.

The best way to publish static build artifacts from AI Studio to Domo is using the end-to-end domo publish workflow, which deploys the validated dist/ directory as a Domo app after enforcing relative asset paths and routing adjustments.