Glossary

Definitions for the terms used across the Appolar docs, admin, and API. If a word is used in a specific way in Appolar, it is defined here.

A – F

Block

The smallest layout unit on a screen. Every block has a type (for example, HeroBanner, ProductGrid, CartSummary) and a set of configurable properties. Screens are composed of an ordered stack of blocks rendered from top to bottom. You add, remove, reorder, and configure blocks per screen in the builder without writing code. See the Block reference for the full list of block types and their properties.

Build

The process of compiling the React Native engine into native iOS (.ipa) and Android (.aab) binaries. A build is required the first time you submit your app to the App Store and Google Play, and again whenever the engine itself changes (new native modules, updated dependencies, changes to the binary entitlements). Most day-to-day changes, including design and layout changes, publish as OTA updates instead and do not require a new build. Appolar uses EAS (Expo Application Services) to run builds in the cloud.

Bundle ID

A unique reverse-domain identifier for your iOS app, for example com.mystore.app. Set when you first create your Apple App ID and Google Play app. The bundle ID is baked into the binary and cannot be changed after your app has been submitted to either store. Choose something you are confident you will keep.

Cohort

A behavioral segment of app users, defined by event conditions. For example, "users who added to cart in the last 7 days without completing a purchase." Cohorts update automatically as users meet or leave the conditions. They can be used as targeting audiences for push notification campaigns and for analytics comparisons. Cohorts are defined in Admin, then Analytics, then Cohorts.

EAS (Expo Application Services)

The cloud build and submission service that compiles Appolar's React Native engine into native iOS and Android binaries. EAS is operated by Expo and managed by Appolar on your behalf. You do not need an EAS account, an Expo account, or any local build tooling to publish your app through Appolar.

G – P

OTA Update (Over-the-Air Update)

A config change that goes live on all users' apps the next time they open the app, without a new App Store or Google Play submission. Color changes, font changes, layout changes, block reordering, and content updates are all OTA. OTA updates are the primary way Appolar merchants iterate on their app after the initial build. An OTA version is created every time you save in the builder.

Preset

A named starting configuration that sets a brand color, font family, border radius, and default block layouts for all screens at once. Presets are a starting point, not a locked style. Every value set by a preset is editable after you load it. Presets are found in the Builder under the Presets tab. See Pick a starter preset for guidance on choosing one.

Renderer

The component inside the Appolar engine that reads a screen's blocks array from the config and renders the corresponding React Native components in order. Every Appolar-powered screen has its own renderer. The renderer pattern is what allows the builder to control any screen's layout without requiring a new build. When you reorder blocks in the builder and save, the renderer on the user's device picks up the new order on the next app open.

Q – Z

Selling Plan

Shopify's data model for subscription products. A selling plan defines a purchase option with a recurring frequency (weekly, monthly, and so on) and an optional discount relative to one-time purchase. Appolar reads selling plan data from the Storefront API and renders the available subscription options on the Product detail screen. See Subscriptions & bundles for setup instructions.

Storefront API

Shopify's public GraphQL API for reading catalog data (products, collections, variants, prices, metafields) and writing cart data. Appolar uses the Storefront API to power all product browsing, search, collection pages, and cart management in your app. You do not need to configure Storefront API access separately; Appolar handles authentication as part of the install flow.

Theme Token

A named design value that flows through every screen in the app. The four core theme tokens are: brand color (the primary action color), font family (one of the 10 curated Google Fonts), border radius (controls the rounding of cards, buttons, and images), and color scheme (light or dark). Changing a theme token updates every component that uses it everywhere in the app simultaneously. Components in Appolar never use hardcoded visual values; they always read from theme tokens.