Important: We've removed this glossary from the site navigation because we've incorporated many of these definitions directly into our articles, but we've left it here in case you still need to refer to it.
Mobify Platform terms #
Below is a list of words and phrases that have special meaning in the context of the Mobify Platform.
We use the term project in two different ways.
- Each PWA based on a website is represented in Mobify Cloud as a Project. When you log into Cloud, you will see a list of your projects, and you can manage them and their bundles.
- The set of files on which a developer works when building a PWA is called a project. Your CSS, images, JS and JSX files are all part of your project. Project files are collected together and uploaded to Mobify Cloud in a bundle.
Progressive Web App (PWA) #
Progressive web apps (PWAs) bring fast, fluid, frictionless mobile experiences that are indistinguishable from a native app. Built into the core functionality of a PWA are techniques that make browsing feel 'native'. Instant page transitions and offline caching mean content is loaded fast on low or no connectivity, without it feeling like a new page is loading each time.
SSR (Server-side Rendering) #
Server-side rendered PWAs have a code bundle which gets run on Mobify’s servers and is usually served from a cache to maximize speed. These PWAs can render content destined for any device, whether it’s mobile, tablet, or desktop. Learn more about server-side rendered PWAs.
The Mobify tag #
<head> tag of any web page using the Mobify Platform.
Mobify Cloud #
Mobify Cloud (https://cloud.mobify.com) is the website that Mobify customers and partner developers use to manage the code for their Progressive Web Apps (PWAs). Mobify Cloud allows you to preview the code created during development and allows you to publish that code when it's ready to go into production.
A bundle is a set of files that transforms your site's layout and performance for mobile. The files for your PWA are collected into the bundle, which is uploaded to Mobify Cloud and served over the Mobify CDN. The bundle will include CSS, images, JSX and JS scripts.
Uploading a bundle to Cloud is called "pushing". There may be several bundles pushed up to Cloud. At any one time, one of them may be "published". The files in the published bundle are used in production. The files in any non-published bundles may be previewed by developers, QA, or testers.
Each bundle has a name that is set when it is pushed. By default, the name is made up from the git hash and repository name, but you can set your own name.
Content delivery network (CDN) #
Production files from a published bundle are available under
The Mobify preview functionality allows you to see changes that you make to your project by just refreshing your local browser, without the need to push a bundle to Mobify Cloud. It works by running a local server on your development machine, and setting cookies that tell the PWA loader to fetch files and assets from that local server. Local preview is described here.
You can also preview a pushed bundle before it's published, using
For tag-loaded PWAs, the terms non-progressive and non-progressive mode refer to Mobify Platform features supported in browsers that don't load the PWA, such as desktop browsers. For example, Mobify's Push Messaging is supported in a Progressive Web App and also for a range of non-PWA browsers. See the guide for non-progressive support. Within the Mobify platform code, non-progressive file and variables use the names non-pwa or nonPWA.
Integration Manager terms #
A Redux thunk action exported by the Integration Manager which is used by front end code to ask the Integration Manager to start some operation (eg. Fetch product page data, login, add to cart, etc.)
The component that conforms to the Integration Manager backend API. It provides a thunk action for each of the commands exported by the Integration Manager.
A Redux action provided by the Integration Manager dispatched by the connector to return data from the underlying website/service that it is built for.
A utility object that ensures that results dispatched by a connector comform to the Integration Manager schema. Type checking only happens in debug builds and is compiled out in production builds so that it doesn't impact bundle size or performance.