Preview and publish

Your App Maker app is functional when you publish it in a preview instance or a deployment.

  • The preview instance lets you see how your app looks and behaves while you are developing it.
  • Publish your app to a deployment to make your app available for use. A deployment is a specific instance of your app that can be run at a specific URL.

To share your app, you can share the URL with your users, as well as publish it to G Suite Marketplace.

Preview your app

You can preview your apps as you develop them to see how they look and behave:

  1. In App Maker, open your app.
  2. Click Preview.

Each developer of an app has their own preview instance, and only you can view the preview instance that you open. When you and another author preview an app at the same time, you see your own versions and don't overwrite each other. If you published a version of your app, previewing a new version does not affect the published version.

When you're in preview mode, you see the app with your own access role. If you defined other access roles and want to test them, you need to publish your app. You can have several deployments, such as Test and Production deployments, to support security testing outside of your production deployment. For details on acess roles, see Define and use roles.

Publish your app

Publish your app to create a functioning deployment that you can use for testing or production:

  1. In App Maker, open your app.
  2. Click Publish.
  3. Select how you want to publish the deployment:

    • publish a new deployment — The default option when you publish an app for the first time.
    • update an existing deployment — Replaces an earlier deployment with the current revision of your app. This action preserves the existing app URL and all other deployment settings.
    • edit your existing deployments — Takes you to Deployments, where you can make more changes before publishing.

    Publishing always deploys the most recent revision of your app. You can also republish an earlier revision. For instructions, see Manage and edit a published app.

  4. If you're publishing a new deployment, enter the following information:

    • Deployment name — Use the name to track deployments. For example, you can publish to test and production deployments of your app.
    • Application access — Choose who can access this deployment. You can grant access to everyone in your domain or just the email addresses you add to the list. You can add a group in Google Groups to this list if:
      • They belong to your domain. You cannot add a public group with a googlegroups.com address.
      • Your Google Account has permission to view the group's membership list.
    • Users with admin access — Enter addresses for users and groups you want to add to the Admins role and to any access roles you created in the app's settings.
    • Google Analytics ID — If you have a Google Analytics account that you want to use for this app, add the account ID to your deployment.
  5. Click Publish. If your app interacts with Google Drive or Cloud SQL, you might need to authorize the deployment.

Once the deployment is published, it's listed on the Deployments screen.

Each deployment is saved as a revision and you can publish older revisions rather than the latest one. Deployments (published apps) don't change as you edit your app. Publish your latest version to test it or give users access to it. Learn more about revision.

Manage and edit a published app

To see and edit your deployments, follow these steps:

  1. Click Publish chevron_right Edit deployments.
  2. Next to the deployment that you want to see or edit, click the Down Arrow expand_more.

You can:

  • View your deployment URL. Share the URL with testers and users.
  • View your app's OAuth scopes.
  • Export database data to a sheet by clicking Export data.
  • View server-side logging data in a new browser tab by clicking View logs. Server-side logs are useful for troubleshooting script issues.
  • Change the deployment app settings by clicking Edit. You can update who can access the app, update database settings, or run bulk data uploads,
  • Replace the published version with a different revision of the app by clicking Republish. The new revision could be the latest (to incorporate the latest changes) or an earlier revision (to revert changes).
  • Delete the app by clicking Delete.

OAuth scopes

Your app uses OAuth scopes to request access to user data and to act on a user's behalf. For example, when your app uses the Drive Picker widget, your app user must allow the app to view and manage their files in Google Drive to open the app. As long as an app's OAuth scopes don't change, a user must grant access only once (the first time they open the app).

Revisions

App maker creates a revision—a specific instance of your app—when you do the following actions:

  • change app settings
  • create, remove, or change a model, script, or page (including page fragments and popups)

You can view, add tags, and manage the revisions of your app.

By default, App Maker publishes the latest revision of your app. If needed, you can publish earlier revisions. Revisions are important when you're managing several deployments, such as test and production deployments, or you need to roll back features.

To manage revisions, from the App Maker editor page click Settings settings chevron_right Revisions.

Databases and deployments

For apps that use a Cloud SQL database, all active instances of an app (previews and published deployments) use the same database by default.

You can change the Cloud SQL instance address in Deployment Settings. When you change database instances, your data models can become out of sync with the database. App Maker detects when this issue happens and helps you reconcile the differences safely.

Publish an app in the G Suite Marketplace

Your G Suite admin can distribute an app to users in your organization (in the same domain) in the G Suite Marketplace.

Before you can publish an app in the G Suite Marketplace:

  • Publish your app in App Maker. Previews of apps can't be distributed in the G Suite Marketplace.
  • Give the G Suite administrator admin access to the deployment so they can manage your app's settings.
  • Review the list of assets and prepare them before you start the publishing process.

To publish in the G Suite Marketplace, a G Suite administrator follows the steps in Publish an App Maker app in the G Suite Marketplace.