Menu
Menu Sheet Overlay
Search
Search Sheet

Glossary of Terms

    Integration Manager terms #

    The Integration Manager is the layer that isolates the frontend code from the backend service integration. It provides a set of Redux actions and JavaScript objects that form its API. Below is a list of words that have a special meaning in the context of Integration Manager.

    Command #

    A Redux thunk action exported by the Integration Manager that 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.)

    Connector #

    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.

    Result #

    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.

    Type #

    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.

    Mobify Platform terms #

    Below is a list of words and phrases that have special meaning in the context of the Mobify Platform.

    Bundle #

    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) #

    The Mobify Content Delivery Network handles all files served from cdn.mobify.com. When a bundle is pushed up to the Mobify Cloud, the files are then available via the CDN.

    Production files from a published bundle are available under https://cdn.mobify.com/sites/<project-id>/production/

    Loader #

    The loader.js file is part of your bundle. The source is available at web/app/loader.js in your project. The loader file is loaded from the currently published bundle by the Mobify Tag.

    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. 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.

    Non-progressive #

    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.

    The Mobify tag #

    The Mobify tag is a snippet of HTML and JavaScript that lets Mobify securely load new code on a web page to optimize the experience for mobile users. The Mobify tag must be included in the source code for the home page and any other web pages that you want to optimize using the Mobify Platform.

    The tag for your project is available via your project’s Tag page on Mobify Cloud. This code must be included inside the <head> tag of any web page using the Mobify Platform.

    Preview #

    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 is published, using preview.mobify.com.

    Progressive web app (PWA) #

    Progressive web apps 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.

    Project #

    We use the term project in two different ways.

    1. 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.
    2. 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.

    SSR (Server-side Rendering) #

    Running a UPWA in the cloud to generate HTML pages that are served directly to browsers. SSR provides faster startup of a UPWA, since the initial HTML for the UPWA is embedded directly in the page.

    See the guide for UPWAs.