App Maker Glossary

Access roles

Sets of users that the app admin grants the same permissions to. The sets can include individual accounts and Google Groups. You can use roles to restrict access to:

Learn more about the built-in Admins role.

App project

A file that you create when you export an app. It has the complete record of how an app is constructed, including the app's data models, scripts, pages, widgets, and access role information.

If the app uses Cloud SQL, the app project file includes the instance name. The app project file doesn't contain app data or role membership, both of which are set in deployments.

App settings

Settings settings in the App Maker UI.

Use to specify application-wide preferences, such as who can edit your app and which roles can control access to the deployed version of your app.

Association

The link between two records through a model relation.

Shown at the top of the page editor. When you click a widget or item in a widget, the breadcrumb navigator shows the item's location in the site relative to its parent widgets. Similar information is in the Outline tab.

Canvas

The central area of the page editor where you build your app pages from widgets.

Code completion

A feature found in any App Maker script and CSS editor. Press Ctrl+Space (Control+Space on Mac) to get code suggestions, descriptions, and examples for scripts and CSS.

Code editor

The script editor that you use to edit scripts and CSS. It supports code completion. You use the code editor when you edit scripts or CSS, including:

  • scripts that open in the large code editor
  • CSS styling
  • data binding expressions
  • event scripts that open in a small code editor dialog
  • any other place where you edit scripts or CSS

Data

In the navigation pane, a list of the data resources available in your app. See model.

Data binding

A link between a widget property and a database property. For example, you can bind the "text" value of a label widget to the "name" field of a record.

Datasource

Defines how a model retrieves and stores data when queried, including the subset of records it returns. For details and examples, see Datasources and Binding widgets to data.

Deployment

A version of your app that is published. It's a specific instance of your app, run at a specific URL. You can have more than one deployment at a time. When you want to deploy a new version, you can update the app at the existing URL or publish another version of the app at a new URL.

Favicon

A small icon associated with your app's website that appears in the browser's address bar and next to bookmarks. Set the favicon in App Settings by providing a URL to the image.

Logic inspector tab

Logic inspector code in the page editor.

A pane where you can view all the data source bindings and code that are attached to the page in the page editor. By showing all of the logic in one place, it's easier to update the logic that's attached to a page.

Model

Data that's available in your app. Model data is organized by records and fields. They correspond to table rows and columns:

  • Records (rows) are data associated with a specific record key.
  • Fields (columns) are the categories of data.

App Maker apps access model data through data sources. See Models.

Module

A subset of pages, models, and scripts exported from an app as a group. You can import modules to other apps. For details, see Reuse apps and modules.

A pane on the left side of the App Maker editor. It shows the app's components under three categories: Data, Pages, and Scripts.

OAuth scope

Defines the app's access to user data. G Suite uses the OAuth 2.0 authorization protocol to allow apps to access G Suite users' data. A separate scope is required for each G Suite service. For example, if your app wants to access the user's Drive files and Gmail, the user must give permission for each service. See OAuth scopes.

Outline tab

Outline in the page editor.

A list that displays the hierarchy of the widgets on the page. You can also hide widgets and lock them in position.

Page

A web page in your app. Edit in the page editor.

Page editor

The pane where you build pages for your apps. The page editor opens when you create or click a page in the navigation pane. It includes the canvas in the center where you edit your pages, and the right sidebar. The right sidebar includes the property editor, style editor, outline, and logic inspector tabs.

Page fragment

A grouping of several widgets into one reusable widget. Use page fragments for app components such as menus and headers. Create by clicking Addadd next to Pages. For details, see Page fragments.

Page selector

A tool in Preview mode. Move between pages in your app by selecting the page from the drop-down list in the top-left corner of the page.

Panel

An area of a page. Each page is a top-level panel that contains all the widgets and features you add to the page. Widgets, page fragments, and popups are also panels and they can contain their own panels for headers, widgets, and other elements.

Panels help with arranging widgets and controlling when widgets load. For details, see Page Layout and Performance Settings.

A preconfigured dialog that your app uses to temporarily display information or prompt a user for a response. Create by clicking Add add next to Pages. For details, see Popups and dialogs.

Preview

A fully operational instance of the latest revision of your app that you can use for preliminary testing. When you click Preview in App Maker, the instance opens in a new browser tab.

Only you have access to the preview instance. You can't share the link with others. To make the app available for others to test or use, publish it to a deployment. For details, see Preview your app.

Preview console

Appears at the bottom of the page when you open your app in Preview mode. As you test your app, the console displays any script and database errors. You can use the drop-down menus to change the information type in the console output.

  • "Error" is the default and shows any errors.
  • "Debug" shows all activity messages associated with your app scripts.

Problems icon

Problems report_problem at the top of the App Maker window.

Appears when the app has one or more errors. The icon's hover text lists the number of errors and number of warnings. Click it to open the Problems dialog, which lists app errors, such as invalid paths and missing API keys, and warnings, such as script issues.

Property editor tab

Property editor create in the page editor.

Used to name a widget, set its layout, set event actions, and control data binding. To use the property editor, open a page of your app and click a widget, including the top-level panel of the page. The settings that are available depend on the type of widget.

Publish

To make an app functional and create a URL for it. You publish an app to a deployment. The deployment has a specific URL that you share with users so they can access the app. You can publish different revisions of the same app to different deployments, such as a test deployment and production deployment. For details, see Publish your app.

Relation

Expresses the potential associations between records in data models. Relations link the record data to each other so that they can be used for data input and display in widgets. For details, see Relations.

Relation end

The group of records in a model that make up one side of a relation. Each relation has two relation ends.

Resource

Any static file such as an image, video, text file, or executable that you upload for use in your app. See Manage resources.

Revision

A deployed version of your app. By default, App Maker publishes the latest revision, but also stores each deployment as a revision. You can revert the published version of your app to a previous revision.

View revisions by clicking All changes saved at the top of the page editor or by clicking App Settings settingschevron_rightRevisions. See Revisions.

Roles

See access roles.

Script

A JavaScript script that runs on either the App Maker's Apps Script runtime environment (a server script) or in the client's browser (a client script). Scripts extend the capabilities of App Maker and enable greater customization. Scripts are listed in the navigation pane. See Scripting overview.

Style editor tab

Style editor palette in the page editor.

A pane that contains the settings that control the appearance of widgets on the canvas. Select a built-in theme and create your own styles with CSS.

Style variant

A specific style for a widget. You can apply different Material Design style variants to widgets as well as create custom style variants. For example, you can specify the background color and shading for a button and set a custom font size for a label. See Widget themes.

Theme

A global style theme for your app. App Maker includes two themes. Use Plain when you want to apply your own CSS to the app. Use Material for Google-like design. See Global style.

Widget

A building block for your app.They include text fields, forms, tables, charts, and layout controls. Drag widgets from the widget palette to the page editor. See Widgets.

Widget palette

Widgets widgets in the page editor.

A window you can open from the page editor. Drag widgets into your page from the widget palette. They're organized by type and include any popups and page fragments that you create.