--- title: "Introduction" slug: "masp-ug-introduction-1-0" updated: 2026-07-06T12:59:49Z published: 2026-07-06T12:59:49Z canonical: "docs.onespan.com/masp-ug-introduction-1-0" excludeFromSearch: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Introduction The Mobile Authenticator Studio app can be customized to meet your needs and enrich the user experience. The [Mobile Authenticator Studio Portal](http://mas.onespan.com) greatly facilitates the self-service customization process. With its highly intuitive user interface it supports customizing and building Android and iOS apps based on your pre-defined customization settings. The portal is hosted by OneSpan and allows single-sign on for your users. It is tenant-based, i.e., your tenant contains only your data and only your users can see your data. The portal is fully compatible with the on-premise variant of Mobile Authenticator Studio. For more information about Mobile Authenticator Studio, see the [product documentation](/mobile/docs/mobile-authenticator-studio-5). ## Basic concepts The following is a list of the basic concepts of the build process with the portal. - Artifact The product of the build process with the Mobile Authenticator Studio Portal, i.e., an app that was built from a set of assets under consideration of the customization parameters. - Asset A file that is used to build the application. - Build Process to build an application with a defined customization, assets, and a builder. The build keeps track of its status (pending, started, finished, cancelled etc) as well as the produced artifact. - Builder A program that combines a customization file with assets to build an app for the target platform of the builder. A builder is for a specific platform, i.e. Android or iOS. > Builders are versioned. Each version might accept different parameters, have different validation constraints, or fix specific issues. - Customization The entire set of parameters you defined. This set of parameters fully controls the look and behavior of the app. - Customization file Collection of parameters in JSON format, has to follow a certain schema. For information about parameters and the required schema and format, see [JSON customization schemas](/mobile/docs/mas-5-ig-json-customization-schemas-5-7-0). - Parameter Variable that controls the appearance and/or behavior of the app to be built, for example the app name, static vector, text color etc. - Target platform The operating system for which the app will be built. Currently supported are Android and iOS. ## Overview of the build process To build and/or customize your app, the portal uses the files and assets you upload to generate the artifacts. The steps to create the build are the same for both platforms. The portal automatically generates the platform-specific artifacts: - AAB and APK files for Android - IPA files for iOS For this process, you need to complete the following steps: 1. Create a Customization file. 2. Prepare the required and optional assets. 3. On the Create Build page, upload the Customization file and assets to start the build process. ![Diagram: Overview of build process in the Mobile Authenticator Studio Portal](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/MASP_Build_Process_Overview.png?sv=2026-02-06&spr=https&st=2026-11-16T15%3A45%3A15Z&se=2026-11-16T16%3A45%3A15Z&sr=b&sp=r&sig=0mQ6Nv2DqGcYmXQlya1OEBD6l%2FvcD%2BK7rGlhWQrgpZE%3D) Overview of the build process in the Mobile Authenticator Studio Portal For more information about the schema definition and examples, see [JSON customization schemas](/mobile/docs/mas-5-ig-json-customization-schemas-5-7-0). For detailed instructions on how to build the app, see [Build a Mobile Authenticator Studio app](/mobile/docs/masp-ug-build-mas-app-1-0).