With two-factor authentication, an additional method beside username and password is required to access an account. Usually this is through a mobile device, using for example a phone number or an app providing a verification code.

An accessibility hint is additional information a user may need to interact with an element. You can think of it as instruction on how to use a control or button. This is particularly important for blind users, user with low vision, users with mobility disabilities and users with memory loss. Missing hints will make your app inaccessible for many users.

For some organizations, providing accessibility labels is mandatory, by law or by policy. In any case they are a good idea.

For example, you have an "Add" button that adds an item to a shopping basket. A good accessibility hint in this case would be Adds the item to the basket. The label "Add" does not say what is added to where, and therefore we need an accessibility hint with the additional information.

Accessibility Labels provide metadata about your app, so that for example screen readers can access the elements in your app. They are critical for blind users, user with low vision, users with mobility disabilities and users with memory loss. Missing labels will make your app inaccessible for many users.

For some organizations, providing accessibility labels is mandatory, by law or by policy. In any case they are a good idea.

Apple has a video, Writing Great Accessibility Labels, which explains more.

An Application Programming Interface is how a computer program talks to another computer program. A specific case is obviously services available on Internet. The computer that offers the API is a server and the program that uses the service is a client.

Engage with businesses and educational institutions to design and build customized apps that meet the unique needs of their organization.

Custom apps are managed with Apple Business Manager and/or Apple School Manager.

The full Apple documentation for custom apps is available at https://developer.apple.com/custom-apps/.

When you make an app available as a template, you are letting other people in your organization use it to make their own apps, based on the design, patchwork and data in the original app.

App Version Management is a platform architecture and set of tools that allow control over features and content that are made available to your users.

A component is a part used to build a view. It can be a functional thing, such as a button or a slider, or just for display, such as an textbox or graph.

Settings for a component can be made to override style settings.

Conditions are used in several places, (most importantly in the if condition type of logic patch) to create a set of rules that generate a result based on a number of keys.

Condition groups are collections of rules used in a condition. They can be combined in a number of ways to create logic structures.

Keys are used in several places, (most importantly in the if condition type of logic patch) to store data to be used in rules to generate a result of true or false.

(Relational) operators are used in used when creating rules in a condition, to give a result of true or false, by comparing two items, or by checking a property of a single item.

Examples:

Rules are used in several places (most importantly in the if condition type of logic patch) to construct a piece of logic that evaluates a number of keys by using one or more operators, which results in a final value of true or false.

Rules can be combined into groups to create even more complex logic structures.

Connections are links between patches and carries data, events and actions from one patch to another.

Connections have different colors depending on the type of connection.

In Appspotr, the term data refers to stored information of various types that is used by an app.

To publish apps with Apple as an organization, you must have a D-U-N-S Number. It consists of a nine-digit identification code. To get a D-U-N-S number you have to request it from Dun & Bradstreet.

D-U-N-S numbers are generally offered at no cost.

More information is available on the Apple Developer support site: https://developer.apple.com/support/D-U-N-S/.

An endpoint is the address to a service, typically a target URL (including a port number, if applicable), which communicates with the network to provide its services.

For example, for the following URL:

http://maps.googleapis.com/maps/api/geocode/xml?address=Rio&sensor=false

the endpoint is

http://maps.googleapis.com

and the rest of the URL is paths and parameters to addess specific services and functions.

Events are a type of output that can be used to make things happen in the app. Typically, they are used navigate between views, but can just as well be used for any purpose you like.

For example, we have a submit button in View A that when pressed opens View B:

Here’s how it would look in Structure Builder:

Files are any media type that is not an that is not an image or an icon.

Files can be uploaded and managed in the Assets tool in the App Editor.

Apps published through the Google Play Custom App Publishing API are private apps that cannot be made public.

The full Google documentation for private/custom apps is available at https://developers.google.com/android/work/play/custom-app-api.

A view or navigation patch can be the home patch for an application. This makes that patch the starting point for the application when it is run.

The home patch is indicated by a house symbol in the top left corner of the patch.

Hypertext Transfer Protocol 2 - HTTP/2 - HTTP/2 is a revision of the HTTP network protocol.

HTTP/2 uses the same methods, status codes, header fields, and URIs, as HTTP, but handles data frames and transport between client and the server differently.

The protocol promises increased request efficiency through minifying resources and performance gains through request prioritization, header compression and multiplexing.

HTTP/2 also allows servers to predict future requests and push data to the client beforehand.

Hypertext Transfer Protocol - HTTP - is a protocol network for distributed, collaborative, and hypermedia communication, mainly on the Internet (World Wide Web).

It is used to exchange or transfer Hypertext - structured text using links between nodes containing text.

An HTTP body is a content part of an HTTP request or response message, containing the bulk of the content of the message.

The body may consist of: * Request line contining the HTTP and target (GET /logo.gif HTTP/1.1 * Response status line, such as (HTTP/1.1 200 OK`) * Additional HTTP Headers * An empty line * Optional data in different types (plain text, JSON, XML, form data, or multipart files and so on)

HTTP headers are fields that can be transmitted as part of HTTP request or response messages. They provide additional parameters or information for the transaction being performed.

An HTTP header consists of a field name for identification and a value containing the data.

More information is available at https://www.iana.org

Hypertext Transfer Protocol Secure - HTTPS is a protocol for secure network communication, mainly on the Internet.

HTTPS consists of communication over Hypertext Transfer Protocol, using Transport Layer Security, or Secure Sockets Layer for encryption.

An icon is an image file small graphical representation of a program, feature, or file. When you click or double-click an icon, the associated file or program opens or an action is performed. For example, if you were to double-click My Computer icon, it would open Windows Explorer. Icons are a component of GUI operating systems, including Apple macOS X and Microsoft Windows.

Good icons are helpful to the user by being an understandable graphical symbol for the thing or action it represents.

Icons can be uploaded and managed in the Assets tool in the App Editor.

Images can be used for any display purpose, such as background in a view, or as illustration in an article.

Images can be uploaded and managed in the Assets tool in the App Editor.

When using images, you can specify how they are displayed by choosing one of several options:

Inputs are connection points in a patches used to communicate or connect with other patches. Typically, they are used to transfer data, but can also be patches or navigation nodes. To be of any use, an input must connect to an corresponding output configured.

For example, let’s say we have a View *A that collects user input for Name and Mobile number. These values can be sent as outputs and used for display in View B, and simultaneously stored in a dataset.

Here’s how it would look in Structure Builder:

By setting up an Integration, you can connect your app to an external service or information store, to bring in data, by accessing an API using REST.

The calls are made using regular API using REST.

Authentication to the API is normally done via a HTTP header.

The integration base URL is the endpoint for making API calls to the service.

It aims to be easy for humans to read and write while maintaining a strict structure to enable simple machine parsing and creation.

More information is available at http://www.json.org/

== Syntax

JSON consists of objects, consisting of a key and a value.

Keys must be strings, written with double quotes: "

Values must be one of the following:

Logic groups are blocks consisting of multiple logic patches that work as small pieces of self-contained logic that create behavior in your app.

Logic groups are indicated by the logic group icon in patchwork.

To view the contents of a logic block, you can click the expand icon in the top left corner. This will show the connected logic blocks and allow you to further configure them.

Logic patches are patches which provide various functions for your app related to working with logic, variables, states or data.

If you connect one or more logic patches together, they will automatically become a logic group.

Navigation in an app is the way a user can use the app, by using features and views, in effect moving through the app.

This structure can be created through drag-and-drop — without coding — by using patches and connections.

Navigation patches are using patches used to create menus, submenus and context menus in an app.

There are two types of navigation patches:

In many menus, you are able to select one of several types to in functions.

In Appspotr, the organization is a collection of people and the apps they create. It can represent a company, for instance a department or unit. An account with Appspotr can have one or more organizations associated with it.

It is best to think of it as a workspace where multiple can work together on creating apps.

Outputs are connection points in a patches used to communicate or connect with other patches. Typically, they are used to transfer data, but can also be events or navigation nodes. In most cases, the receiving and must also have a corresponding input configured.

For example, let’s say we have a View A that collects user input for Name and Mobile number. These values can be sent as outputs and used for display in View B, and simultaneously stored in a dataset.

Here’s how it would look in Structure Builder:

Patches are nodes used to construct the application workflow, created with the Patchwork tool in the app editor.

These nodes are connected to each other through inputs and outputs.

Patches can be used with connections to create a navigation.

Patchwork is perhaps the most important tool in Appspotr 3. It is used to create the core of the application - the behavior.

By combining different views and logic-blocks to each other through patches, you can set up input and output properties, and the workflow of the application.

Permissions govern what you ara alllowed to do. Depending on the permissions you have, you will have access to different areas, and be allowed to do different things in those areas.

For app administrators in Appspotr 3, permissions are assigned to various roles, which users then can belong to in order to be granted those permissions.

As you can see, this may mean that you need to set multiple permissions before an action will work.

A progressive web application (PWA) is a type of application software delivered through the web, built using common web technologies including HTML, CSS and JavaScript. It is intended to work on any platform that uses a standards-compliant browser, including both desktop and mobile devices.

Since a progressive web app is a type of webpage or website known as a web application, they do not require separate bundling or distribution. Developers can just publish the web application online, ensure that it meets baseline "installability requirements", and users will be able to add the application to their home screen. Publishing the app to digital distribution systems like Apple App Store or Google Play is optional.

REST - Representational State Transfer is a lightweight protocol for HTTP communication, where parameters are mostly encoded in the request URL.

Optionally, parameters can also be sent in the message body.

The term RESTful basically means the same as REST, but sometimes is used to mean web services that implement REST methods and architecture.

A REST Method is an HTTP method used to access a resource.

REST Requests are calls to a REST service.

REST Request can include HTTP Headers and parameters.

A Resource is a part of the target URL, referring to the object to be accessed with REST methods.

For the URL

+ http://maps.googleapis.com/maps/api/geocode/xml?address=Rio&sensor=false +

the resource is

` /maps/api/geocode/xml `

App Administrators can belong to different roles, which provides them with different levels of access to the app management.

Roles are created and configured for the organization, and can then be used in any apps belonging to it.

Some examples:

Admin — The admin roles gives access to all parts of the organization or app.

App Owner — An app owner can do everything related to the app including create new apps, publish apps and buy licenses.

Developer — A developer can do everything an app owner can do except buy new licenses and create new apps.

App Manager — An app manager can update content in datasets, media library, push notifications, app users, app admins and view analytics.

Designer — A designer can update content in datasets, media library, push notifications, view analytics and change the design.

Content Agent — A content agent can update content in datasets, media library and push notifications.

Member — A member has no cms access, but may be given access to various functions inside the app.

External — External users have no cms access to the app, and typicall have no special app access.

A State is the current condition or status of an object or component. It can for example if a button has been turned on or off, if a view has been visited, a property has certain value, and so on.

States can be accessed and managed with a State logic block in Patchwork.

A Storage TBD

= Style :doctype: article :keywords: glossary, Style :description: glossary, Style

A Style is the design that applies to the entire app and governs how it looks to the user. Think of it a s a template for views and components.

You can create multiple styles and select one as the current for the app.

A Variable TBD

= Version :doctype: article :keywords: glossary, Version :description: glossary, Version

The version is a way to categorize the states and capabilites of software, indicated by a combination of numbers. It is a handy way to know which pieces of software will work with what other piece of software.

In Appspotr, you need to distinguish between Platform Version and the App Version. Also, the PWA version work slightly different from native apps.

The app version is the current state of an app. A few things get compiled into a version:

The platform version is the underlying code that the App and CMS are running on. It follows semantic versioning.

If your app is on Platform Version 0.16.1, the CMS will also be adapted for 0.16.1.

Given a Platform Version of 0.16.1, this is how those numbers are broken down:

Changes to Major and Minor versions of Appspotr will include updates to your app that require you to run an app Update and rebuild for App Store & Play Store. Your users will have to update their apps to see new content and features made for this new Platform Version.

Patch updates will happen regularly for the latest Platform Version and will automatically be applied to all apps running on the affected Platform Version. Rebuilding for App Store & Play Store are optional, the apps will keeps themselves on the latest Patch version automatically. The benefit of rebuilding is that the starting Platform Version of the user’s app will be more up to date and not need to auto-update itself.

A View is what is displayed to the app user at a particular point in time while using the app.

Settings for a view can be made to override style settings.