Skip to main content

Managing Apps

This section provides tools to view, edit, and maintain your created AI Facial Skin Analysis apps. From here, you can access app configurations, manage SDK settings, enable advanced features such as recommendations. Each app card under Your Apps offers quick actions which let you preview, edit, or delete apps.

Open AI facial skin analysis → Your Apps in the Fynd Console. Each card shows the app name, Application ID, creation date, and Active/Inactive status. Copy Application ID copies the identifier for your integration.

Skin Analysis app cards in Fynd Console with preview, options, and activation controls
  • Preview (▶): The Preview feature allows you to test and experience your Skin Analysis app before deploying or sharing it publicly. It helps verify the app’s functionality, flow, and report generation process in real-time.
    When you click the Preview (▶) button on any app card, a popup window appears with two options for accessing the app:
    • View on Smartphone: A QR code is automatically generated. Scan this QR code using your smartphone’s camera to open and test the app directly on a mobile device. This lets you simulate the end-user experience, perform a live skin analysis, and review how reports are generated on smaller screens.
    • Using Share Link: A shareable URL is also displayed in the same window.
      You can use this link to preview the app in a web browser or share it with team members, testers, or clients for review.
      Clicking the link launches the Skin Analysis app, allows users to start a facial scan, analyze results, and generate a full Skin Analysis report.
  • Options (⋯): Each app card in the Your Apps section includes an ellipsis (⋯) menu in the top-right corner. Clicking this icon opens a list of management actions that let you modify or remove your Skin Analysis apps:
    • Edit: Modify app configurations such as data storage, report parameters, or recommendations. We’ll discuss editing apps in detail in the next section.
    • Delete: Permanently remove the app from your account. Once deleted, the app and its associated configurations cannot be recovered.
  • App activation status: Each app card includes a status toggle to mark the app as Active or Inactive. Active apps display an Active label and are available for preview, testing, and sharing. Inactive apps display an Inactive label and are temporarily disabled.
    You can toggle an app’s status anytime to control its availability without deleting it.
note

Use activation toggles to manage which apps are live for testing or client demos.

Editing the App​

This section allows you to view, manage, and modify configurations, reports, and other advanced settings associated with the selected Skin Analysis app.

The workspace contains Subjects, Recommendation, SkinGPT, Integration, and SDK configuration. Skin GPT apps also include Routines. Configuration, catalog operations, assistant settings, routines, and activation are saved separately.

Subjects​

The Subjects tab provides access to skin scan reports generated through your Skin Analysis app. Each subject has a unique Subject ID and can contain multiple scan reports, making it easy for you to track, review, and manage individual results.

This section acts as the central record of all analysis activities, whether you're monitoring usage, reviewing scan quality, performing audits, or exporting reports for internal review. From here, you can open detailed reports, download them for offline use, or remove outdated or test scans to keep your data organized.

Subject card metadata with illustrative example portraits, subject identifiers, and available scan reports

Viewing reports:

  • The list of reports is organized by subjects. A subject card shows its last scan time and number of available reports.
  • Select the Subject ID or subject card, then open the required scan in its scan list to view the detailed Skin Analysis Report.
  • The report includes detailed metrics, detected skin conditions, annotated images, and other analytical data for that specific scan.
Scan reports available for a selected Skin Analysis subject, with an illustrative example portrait

Downloading reports:

  • Open a scan report and use Export report to download the complete report as a PDF. The scan table also supports exporting scan records to CSV.
  • The downloaded report can be used for offline reference, sharing with clients, or internal review.
  • The PDF includes the available report parameters and visuals configured earlier in the Report Setup section.
  • PDF export is unavailable after the report's retention period ends. Changing the current retention setting does not establish that older assets remain available.

Deleting reports:

  • Select reports in the scan table and use its deletion action. Subject deletion is separate: delete an individual subject or selected subjects from the Subjects page.
  • A confirmation dialog will appear before deletion. Once confirmed, the report is permanently deleted and cannot be recovered.

Recommendation​

The Recommendation module acts as a curated product mapping system, linking skin issues to relevant products. Once configured, GlamAR’s AI model analyzes skin parameters (like acne, wrinkles, and pores) and returns tailored product suggestions directly in the final skin analysis report.

Additionally, you can import product data in bulk to streamline setup and make sure that recommendations remain accurate and comprehensive.

Set up the product catalog​

If the catalog is not ready, follow Set up catalog. The Console shows setup progress and a ready, failed, or still-setting-up state.

  • While setup is running, wait for the catalog to become ready before importing products.
  • If setup fails, use the available retry action.
  • If the page says the catalog is not included in your plan, resolve the account entitlement before adding products.
  • Turning on Product recommendation in Report setup controls the report section. It does not replace catalog setup or import.

Importing Product Data

CSV upload is supported; the other listed integrations are not yet available.

  1. CSV Upload (currently supported)

    • Open Import → Bulk Import, select CSV, and click Next.
    • Use Download Sample for the expected template, then add the completed file with Upload File.
    • Resolve validation messages, continue with the import, and check its processing status.
    • Supported File Type: CSV
    • Maximum File Size: 1 MB
    • Products per upload: 1–500.
    • Required columns: SKU, IMAGES, TITLE, with values supplied for each product. Resolve duplicate SKUs before continuing.

Open Import → Upload History to review validation and processing results. Parsing a file successfully does not mean its import has completed.

Skin Analysis catalog import mode selection with CSV available and other platforms marked coming soon
Skin Analysis CSV import with Download Sample, Upload File, and the 1 MB file limit
  1. Future Integrations (coming soon)
    • Fynd Platform and Shopify are listed as coming soon. They are not available import methods in this flow.

Recommendation table

Once product data is imported, it appears in a structured table that allows you to review, manage, and refine each entry. This table provides a quick snapshot of essential product attributes and how they map to the AI recommendation engine. Each column plays a specific role in ensuring accurate matching and high-quality recommendations.

Skin Analysis recommendation catalog with product metadata and actions
ColumnDescription
TitleShows the name of the product exactly as it will appear in user reports. A clear, descriptive name helps users quickly recognize the product.
SKUA permanent, unique identifier used for tracking and internal mapping. Once uploaded, SKU IDs cannot be changed, and GlamAR uses them as the anchor for all product-level operations.
CategoryDefines the product type (e.g., Cleanser, Serum, Moisturizer), helping the AI match skin concerns to the correct solution category. Accurate categories improve the relevance of recommendations.
AM/PMIndicates when the product is intended to be used: AM, PM, or Both. Assign the value from the product's usage instructions.
Skin typeSpecifies which skin types the product is suited for: Oily, Dry, Combination, or Normal. Providing accurate skin type metadata greatly enhances recommendation precision.
ConcernLists the specific skin issues the product targets, such as Acne, Wrinkles, or Pigmentation. These fields directly influence the AI's decision-making and are among the most important for matching.
ActionsAllows you to edit or delete each product entry. Use this to refine product details, correct metadata, or remove outdated products from the recommendation pool.

Testing recommendations

Next to the Import button (at the top-right of the table) is a Play button, which lets you preview and simulate how GlamAR’s AI model generates product recommendations. This feature is especially useful for validating your product metadata before publishing changes. It allows you to test different skin profiles and immediately see which products the AI selects, along with the product metadata shown in the current results table.

When you click the Play button:

  1. A popup window opens with input options.
  2. Select your Skin Type from the available choices:
    • Normal
    • Oily
    • Dry
    • Combination
  3. Select the specific skin parameters and issues to include in the analysis, such as:
    • Acne
    • Pores
    • Wrinkles
    • Eye bags
    • Dark circles
    • Post acne scars
    • Whiteheads
    • Pigmentation
    • Hydration
  4. Click Get Recommendation.
Recommendation test with skin-type selector, concern checkboxes, and Get Recommendation action

The system then lists the products returned for the selected criteria. The current results table displays Title, SKU, Category, Skin type, Concerns, and AM/PM. These test inputs are separate from a captured scan.

Products returned by a Skin Analysis recommendation test

Best practices:

  • Keep your product catalog updated to ensure recommendations remain accurate and aligned with current inventory.
  • Regularly test recommendations using the Play button to evaluate AI performance and mapping accuracy.
  • Use descriptive product names and categories to help the AI deliver more precise results.
  • Ensure the CSV file adheres to the correct format and includes complete information (Product Name, SKU ID, Category, etc.) for seamless import.

Editing product entries

Each entry in the Recommendation table can be individually edited to update or refine product information. Editing helps ensure that product details, targeting parameters, and metadata remain accurate for AI-driven recommendations.

When you click the edit icon in the Actions column of a product entry, an editing panel opens with the following grouped options:

Basic Details​

This section includes core product information used to display items inside skin analysis reports and to manage your catalog efficiently. Several of these fields also influence how GlamAR’s AI model evaluates and recommends products, especially when paired with skin concerns.

SKU (Required / Non-editable after upload)

The SKU ID uniquely identifies each product in your catalog and is used internally to link recommendations, analytics, and performance data. Because this field must remain constant across uploads, choose a clear and consistent SKU format. Once imported, SKU IDs cannot be changed.

Title (Required)

This is the name shown to users in recommendations. Use descriptive, easy-to-read names that clearly differentiate variants (e.g., “Hydrating Cleanser - Fragrance Free” instead of internal codes). Consistent naming conventions improve overall user clarity.

Images (Required)

At least one image is required, and the editor accepts up to three. A product image is necessary for displaying the recommendation visually. Use a clean, clear photograph of the actual product packaging. Square images (1:1 ratio) provide the best balance and prevent distortion in the report layout.

Product URL

This link opens when a user clicks on a recommended product inside their skin report. Use direct, product-specific URLs so users land exactly where they can read more or purchase the item. This improves conversion rates and reduces navigation friction.

Currency, MRP and Selling Price

These pricing fields define the product’s cost and value positioning.

  • Currency: Select the currency code (USD, INR, AED, etc.).
  • MRP: The official retail price.
  • Selling Price: The current price after discounts or promotions.
  • MRP and Selling price accept non-negative values.

Accurate pricing helps GlamAR showcase correct value comparisons and can influence how the AI weighs certain recommendations, especially if multiple products meet the same concern criteria.

Brand (Read-only / AI-Enhanced)

The Brand field is read-only in the current editor. The brand field indicates which company or product line a product belongs to. Keeping brand names consistent across entries helps maintain a clean visual presentation and allows the AI to associate credibility or relevance based on your internal brand positioning.

Category (AI-Enhanced)

The category defines the product’s functional type, such as Cleanser, Serum, Toner, Moisturizer, Mask, etc.
This field has a strong impact on AI recommendations. The AI uses categories to identify which products are appropriate for specific concerns. For example:

  • Acne-prone users may be shown anti-acne serums or clarifying cleansers.
  • Users with pigmentation may receive Vitamin C serums.
  • Dryness concerns often map to hydrating moisturizers.

Use standard skincare categories to ensure the most accurate recommendations.

Performance and Feedback​

The Performance and Feedback fields help GlamAR understand how well each product performs within your catalog. These values influence how the AI prioritizes products when multiple options address the same skin concern. Well-maintained feedback fields improve the quality, ordering, and relevance of recommendations seen by the user.

Popularity Score (AI-Enhanced)

The popularity score reflects how well a product performs relative to others in your catalog. This can be based on sales volume, user engagement, or internal ranking systems. A higher score tells the AI that users tend to prefer this product, which can lead to it being shown more prominently when recommended. For example, two moisturizers that target dryness may both be eligible, but the one with a higher popularity score is more likely to appear first.

tip

Keep the scoring consistent across your catalog, use a 1–5 range.

Average Rating (AI-Enhanced)

This represents the aggregated rating users have given the product on your platform (e.g., 4.5/5). The field accepts values from 0 to 5. Higher ratings can improve a product’s visibility within GlamAR recommendations, especially when several products address the same concern.

Ratings also help users trust recommendations since they provide a familiar quality indicator. Use values from your product-rating records rather than inventing a customer rating.

Details​

The Details section contains descriptive attributes that help users understand the nature, purpose, and formulation of each product. While not all fields directly influence the AI model, these details contribute to a richer, more informative recommendation card and help maintain a polished, professional appearance in the final report. Completing these fields thoroughly ensures users have enough context to evaluate whether a product suits their needs.

Description (AI-Enhanced)

The product description provides a short summary about what the product does and why it’s beneficial. This text appears in the final recommendation, helping users quickly understand the product’s purpose without leaving the report. Use concise, benefit-focused language, for example:
“Fragrance-free hydrating cleanser.” The current field accepts up to 40 characters.

A well-written description improves readability and user engagement, especially when your catalog contains several similar products.

Keywords (AI-Enhanced)

Keywords are short tags that describe product attributes, benefits, or key ingredients. These fields directly help GlamAR’s AI understand the product’s characteristics and improve its ability to match products to specific skin concerns.
Examples include: “hydrating,” “vitamin c,” “anti-acne,” “fragrance-free,” “brightening.”

Including strong, relevant keywords is one of the easiest ways to boost AI recommendation accuracy. Aim for 5–7 meaningful keywords per product. The field accepts up to 10 entries, with up to 50 characters per entry.

Ingredient list (AI-Enhanced)

Record ingredients from the product's stated formulation. The field accepts up to 10 entries, with up to 50 characters per entry.

Size / Volume (AI-Enhanced)

This field indicates the quantity of the product, such as 20 ml, 50 ml, or 100 ml. Displaying this information helps users understand product value and prevents confusion, especially when similar products come in multiple sizes.
Use standard units to maintain consistency across your catalog.

Packaging Type (AI-Enhanced)

Packaging style describes the physical form of the product such as bottle, tube, jar, pump, or dropper.
This field is marked as AI-enhanced and improves the user experience by highlighting attributes that many shoppers care about. For example, pump dispensers may appeal to users who prioritize hygiene, while tubes may be preferred for travel.

Providing this detail also helps your catalog feel more complete and professional.

Usage and Targeting

The Usage and Targeting fields are some of the most influential elements in determining how GlamAR’s AI matches products to each user's skin concerns and routine needs. These fields describe who the product is for and how it should be used. Supplying accurate and complete values here significantly improves the precision and trustworthiness of recommendations.

AM/PM (AI-Enhanced)

This field specifies when the product should be used, AM (Morning), PM (Night), or Both. GlamAR uses this information to avoid suggesting routines that conflict with common skincare rules (such as recommending retinol during the day).
Assign usage timing thoughtfully:

  • AM examples: Vitamin C, Sunscreen, Lightweight gels
  • PM examples: Retinol, Night creams, Exfoliants
  • Both: Moisturizers, cleansers, soothing serums

Including this ensures recommendations align with safe and effective skincare practices.

Skin Type (AI-Enhanced)

Indicates which skin types the product is suitable for: Oily, Dry, Normal, or Combination. Sensitive is not available in the current selector. This is one of the most important matching fields for GlamAR’s AI. Accurate skin type mapping helps the system avoid unsuitable suggestions (e.g., heavy creams for oily skin).

You can assign multiple skin types when appropriate, such as for mild, hydration-focused products.
Using the standard values from your CSV ensures compatibility.

Concerns (AI-Enhanced)

Lists the specific skin concerns the product addresses. Examples include:

  • Acne
  • Wrinkles
  • Pigmentation
  • Pores
  • Hydration
  • Dark Circles
  • Eye Bags
  • Post acne scars
  • Whiteheads

This field signals to the AI which problems the product claims to solve.
Accurate concern tags provide matching information. They do not guarantee a particular recommendation rank, and the current test table does not show confidence percentages.

tip

Be accurate and conservative. Avoid tagging every concern just to increase visibility. This weakens the AI’s matching logic.

Gender (AI-Enhanced)

Specifies the intended audience: Male, Female, or Unisex.
The field is marked as AI-enhanced and helps refine the user experience when presenting products from gender-specific skincare lines. If your products are broadly applicable, set the value to Unisex.

Description and Metadata​

The Description and Metadata fields add structure, nuance, and clarity to your product catalog. While some of these fields may not directly influence the AI model, they help GlamAR present a more complete, organized, and context-rich recommendation experience. They also play a role in grouping related products and highlighting important formulation characteristics that users often look for.

Grouped SKU

Group SKU connects products that belong to the same family or variant line.
For example, a hydrating moisturizer available in 50 ml and 100 ml formats should share the same Group SKU.
This helps GlamAR understand product relationships and improves the AI’s ability to:

  • Recommend the most relevant variant
  • Avoid suggesting duplicate items
  • Maintain consistency in product families

Using Group SKU is especially helpful in large catalogs where multiple variants exist.

Product label

Product Labels act like category tags or badges that characterize the product, such as Bestseller, New Launch, Dermatologist Recommended, Anti-Aging, or For Sensitive Skin.

GlamAR uses these labels to enrich the product representation and improve sorting logic.
Labels also appear visually in user-facing recommendations, helping products stand out and build trust.

Choose labels that reflect real marketing positions or clinical claims.

Fragrance Free / Alcohol Free / Paraben Free

These boolean fields (Yes/No) indicate important formulation details that matter to many users, especially those with sensitive or reactive skin.

Including these fields:

  • Helps users quickly identify products compatible with their needs
  • Adds transparency and clarity
  • Improves the perceived safety of the recommendation

These three formulation fields are marked as AI-enhanced. Review each value against the manufacturer's stated formulation.

pH Level

Represents the product’s pH value, which can be helpful for categories like cleansers, exfoliants, or toners.
Enter the product's documented value from 0 to 14 rather than assigning a standard value.

Users may not see this value prominently, but including it contributes to a more detailed and trustworthy catalog entry.

AI-Enhanced Fields in Product Recommendations​

Some fields in the product catalog are marked with an AI icon in the UI. These fields can be partially or fully populated using GlamAR’s AI enrichment tools. AI-enhanced fields help improve the completeness, consistency, and accuracy of your product metadata.

What AI-Enhanced means:

  • GlamAR can assist in generating or suggesting values for these fields.
  • The AI icon does not replace required-field validation or confirm that a generated value is correct.
  • Missing optional metadata leaves less product information available for matching; filling it does not guarantee a particular score or rank.

Examples of AI-Enhanced fields:

  • Brand (read-only in this editor)
  • Category
  • Popularity score and Average rating
  • Description, Keywords, and Ingredient list
  • Size / Volume and Packaging Type
  • AM/PM, Skin type, Concerns, and Gender
  • Fragrance free, Alcohol free, and Paraben free

Grouped SKU, Product label, and pH level are not marked with the AI icon in the current editor.

AI-enhanced fields are especially valuable if you upload a large catalog and want GlamAR to assist you in enriching product metadata quickly.

tip

Even when AI can fill fields for you, review and adjust the values to ensure they match your internal product standards.

Click Publish in the product editor to save product changes. This updates the catalog product, not the app's SDK configuration.

Routines​

The Routines page is available for Skin GPT apps. It defines the steps and products used in a skincare routine.

Create and edit a routine​

  1. Select Create Routine.
  2. Enter a routine name.
  3. Choose Morning (AM), Night (PM), or Both AM + PM.
  4. Add, remove, and reorder the steps.
  5. Configure each step in Product or Keyword mode.
  6. Click Save.

When using Both, configure the morning and night steps in their respective tabs.

SettingLimit or behavior
Routine nameRequired; maximum 255 characters.
Step nameMaximum 100 characters.
Step descriptionOptional; maximum 256 characters.
Product modePin up to five specific products per step.
Keyword modeUse ingredient, benefit, or attribute keywords to match products dynamically.

Activate or remove a routine​

Use the routine's status toggle to activate it. Only one routine can be active at a time; activating another turns the others off.

Saving the routine and activating it are separate actions. Use the delete action and confirm when a routine is no longer needed.

The Routine questions tab configures the user's intake questions. It does not define these routine steps.

SkinGPT​

SkinGPT is an AI-powered virtual skincare assistant that provides personalized responses, product recommendations, and expert guidance, all based on the user’s individual skin scan results. By connecting the AI assistant to your Skin Analysis app, you can offer users an engaging, conversational experience that delivers tailored insights and suggestions in real time.

SkinGPT uses data from the user’s skin analysis, including detected conditions, skin type, tone, and concerns to generate intelligent, context-aware replies.

Users can ask questions about their results, learn more about their skin health, and receive actionable advice or product recommendations directly within the app.

Setup

Open SkinGPT in the app workspace. If the assistant has not been set up, click Launch SkinGPT. This opens the SkinGPT setup, where you can define your assistant’s appearance, personality, and user interaction behavior.

The assistant configuration is separate from the Skin GPT integration mode and its entry-screen controls. An SDK app can also have a configured assistant.

Basic Info

These settings help personalize the branding and identity of your SkinGPT assistant.

  • Logo: Upload a logo to represent your brand within the chat interface.
    • Supported formats: PNG, JPG/JPEG, SVG, or WEBP
    • Maximum file size: 1 MB
    • Recommended aspect ratio: 1:1
    • Use the trash icon on the uploaded logo to remove it before adding a replacement.
  • SkinGPT Name: Provide a custom name for your AI assistant. This name will appear at the top of the chat window and in messages, helping users recognize your brand’s voice. Required; maximum 30 characters.
SkinGPT Basic Info with logo and empty name field

Define Persona

This section defines your SkinGPT’s behavior and tone of communication. Use this space to describe how your assistant should interact with users.

  • Write a detailed description of your business, brand identity, and how SkinGPT should behave during conversations.
  • Maximum character limit: 10,000
note

A well-defined persona ensures your AI delivers consistent, brand-aligned conversations.

Welcome Content

Customize how SkinGPT greets users and initiates interaction for a seamless, engaging experience.

  • Title: The main greeting or headline (e.g., “Welcome to your personal skincare assistant!”).
  • Welcome Subtitle: A short, supportive line that encourages users to start chatting (e.g., “Ask me anything about your skin analysis report.”).
  • Conversation Starters: Add example questions or prompts to help users begin the conversation.
    Example: “What does my skin report say?” or “Recommend a moisturizer for oily skin.”
  • Auto Suggestions: Toggle to enable or disable to control whether dynamic follow-up questions or recommendations appear after each SkinGPT response.
    When enabled, the AI automatically generates context-based suggestions to guide the next steps in the chat.

The Title accepts up to 50 characters, the Subtitle up to 100, and Conversation starters up to five prompts.

Best practices:

  • Keep your persona description focused on your target audience’s tone and needs.
  • Ensure conversation starters are relevant to your skin analysis workflow and frequently asked questions.
  • Use a high-quality logo with a transparent background for professional visual consistency.
  • Test SkinGPT’s greeting and flow through the preview feature before going live.

Use the assistant section's Publish action and confirmation to save assistant changes. This does not publish unsaved SDK configuration edits.

Integration​

Open Integration for the setup offered for the app's platform. Follow the displayed instructions and the Skin Analysis integration documentation for your SDK or plugin.

Keep the Application ID associated with the app you intend to use. Test the saved app before placing the integration on a customer-facing page.

SDK Configuration​

The SDK Configuration section consolidates all configuration options necessary to fine-tune how your Skin Analysis app integrates and operates within the GlamAR SDK environment.

Most of the options available here have already been discussed in detail under:

  • App Details
  • Face Scan Instructions
  • App Appearance
  • Report Setup
  • Routine questions (Skin GPT apps)

All previously configured settings such as typography, themes, data storage, and report customization are accessible here for quick updates or review without navigating back to individual tabs.

Advance settings​

The Advance settings tab provides deeper control over your app’s user interface (UI) and behavior. These settings allow you to toggle certain UI components and adjust SDK behavior directly via configuration or code.

Skin Analysis Advance settings with Back Camera

You can enable or disable key user interface actions using simple toggles:

  • Allow back: Toggle on/off to show or hide the back navigation option within the try-on or analysis window.
  • Allow close: Toggle on/off to include or remove the close (exit) button in the interface.
  • Allow share: Toggle on/off to enable users to share their analysis results or reports.
  • Allow full screen: Set whether the experience can show a fullscreen control on supported devices.
  • Allow global cart: Show or hide the cart action in the experience's top navigation. This is separate from Add to cart on a recommendation card.
  • Allow global wishlist: Set the visibility preference for a global wishlist entry where the selected experience supports it.
  • Allow price: Set the general product-price visibility preference. Skin Analysis recommendation and routine cards have separate Selling price controls in Report setup.
  • Allow product name: Set the general product-name visibility preference where supported by the selected experience.
  • Allow wishlist: Set the visibility preference for an individual product's wishlist action, separate from the global wishlist entry.
  • Back Camera: Prefers the rear camera when Skin Analysis capture starts. Switching it off prefers the front camera. Available on supported devices. This setting does not add a camera-switch button.
note

These toggles are primarily used to tailor the in-app experience, controlling navigation and interaction availability.

Code Editor​

For developers or advanced users, the Code Editor provides access to the app's custom configuration JSON at appConfig.ui_config.customCode, not the whole app configuration. You can modify behavioral and UI-level parameters here to customize the app experience further. Use valid JSON objects and preserve existing keys.

Parameters:

ParameterTypeNew-app value or runtime fallbackPurpose
allowToastBooleantrue when omittedSet to false to suppress SDK toast notifications.
openLiveOnInitBooleanfalseDetermines whether the live camera view should automatically open when the app initializes. Set to true to start the live view immediately on load.
captureIQ.enabledBooleantrue in new appsSet to false to disable CaptureIQ route selection.
captureIQ.routes.skinAnalysisBooleantrue in new appsSelects CaptureIQ for Skin Analysis when enabled.
captureIQ.routes.skinGptBooleantrue in new appsSelects CaptureIQ for the SkinGPT capture flow when enabled.
captureIQ.retakeRedirectString"home"Retake destination: "home" or "camera".
retakeRedirectString"home" fallbackOlder top-level retake setting; prefer the nested CaptureIQ setting for CaptureIQ.
popUpOverrides.quitBooleanfalseControls whether the Quit Confirmation popup appears when users try to exit the app. When set to true, the popup is disabled.
popUpOverrides.resultBooleanfalseToggles the Results Summary popup that appears after completing an analysis. When true, this popup is disabled.
popUpOverrides.restartBooleanfalseDetermines whether the Restart Confirmation popup appears. If true, the popup will be disabled, allowing instant restart.
screenOverrides.heroScreenBooleanfalseEnables or disables the Hero Screen (intro or splash screen) displayed when the app starts. When set to true, this screen is skipped.
skinAnalysis.showNavBarBooleantrue fallbackControls visibility of the navigation bar in the Skin Analysis result screen.
screenOverrides.domainBlockBooleanfalseSuppresses the domain-block screen.
screenOverrides.billingBlockBooleanfalseDetermines whether the Billing Block screen appears (shown when subscription or billing issues occur). When true, this screen is suppressed.
screenOverrides.cameraFailedBooleanfalseToggles the Camera Failed error screen, which appears when the device camera cannot initialize or connect. When true, this screen will be disabled.
screenOverrides.cameraAccessDeniedBooleanfalseControls whether the Camera Access Denied message is shown when user permissions are not granted. When true, the warning is hidden.
screenOverrides.somethingWentWrongBooleanfalseToggles the fallback Something Went Wrong error screen, displayed for unexpected runtime or SDK-level errors. When true, the screen is disabled.
Configuration tips:
  • Use true to disable popups or screens and false to keep them enabled.
  • It’s generally recommended to keep error and access-related screens enabled (false) for debugging or troubleshooting purposes.
  • The toast notifications and popups can be re-enabled easily without requiring a full SDK redeployment, simply toggle the parameters and save.
  • Test your configuration changes using the Preview option before publishing to production.

Screen overrides change the displayed interface. They do not grant camera permission or resolve an underlying domain, billing, or camera error.

For the popUpOverrides and screenOverrides switches listed here, true suppresses the corresponding popup or screen and false leaves it enabled. This pattern does not apply to every configuration key: allowToast, for example, uses false to suppress toast notifications.

Keep error and access-related screens enabled while troubleshooting so users and testers can see the reason a flow stopped. To restore a popup or screen, change its override back to false, publish the app configuration, and start a fresh preview session. These configuration changes do not require deploying a new SDK build, but they still need to be saved and tested.

For example, merge this CaptureIQ configuration into the existing editor content:

{
"captureIQ": {
"enabled": true,
"retakeRedirect": "home",
"routes": {
"skinAnalysis": true,
"skinGpt": true
}
}
}

CaptureIQ is selected when its route value is exactly true and captureIQ.enabled is not false. The initial camera still comes from Back Camera.

For CaptureIQ, the nested retake setting takes precedence over the older top-level value. Automatic-start or introductory-screen overrides can keep a retake in the camera flow.

Publishing the Changes​

Once all configurations and edits are complete, you can make your updates live by clicking the Publish button located at the top-right corner of the interface.

For SDK configuration:

  1. Complete your changes and resolve validation errors.
  2. Click Publish at the top right. It becomes available when the form has changed.
  3. Confirm Yes in the Publish dialog.
  4. Wait for the success message.
  5. Open a fresh Share Link or QR session and check the saved behavior.
Publish confirmation dialog with No and Yes actions

What happens on publish?

  • The latest changes to App Details, Face Scan Instructions, App Appearance, Report Setup, and advanced SDK configuration are saved by the SDK configuration Publish action. Catalog products, SkinGPT, routines, and app activation have separate actions.
  • Open a fresh Share Link or QR code session after publishing to verify the saved settings. An already-open session may not reload the configuration.
Important notes:
  • Review all configurations before publishing to avoid overwriting active settings.
  • Publishing replaces the current live version with the newly updated configuration.
  • Once published, you can preview and test the live version again using Preview under Your Apps.

If publishing fails, correct the error and retry. Leaving with unsaved edits can show a Save changes? dialog.

  • Save Changes submits the edited form for saving. Check for the success message or resolve any validation error before leaving.
  • Go Back continues to the destination without saving the edits.
  • The × closes the dialog and keeps you on the editor so you can continue editing.
Save changes prompt shown when leaving an edited form, with Go Back and Save Changes buttons
ActionScope
SDK configuration PublishSaves the app's settings.
App-card Active / InactiveChanges the app's enabled status.
SkinGPT PublishCreates or updates the assistant configuration.
Routine SaveCreates or updates a routine.
Routine status toggleSelects which routine is active.
Catalog import or product PublishUpdates the catalog through its own workflow.

Publishing app configuration does not deploy a new SDK build or establish that an already-open session has reloaded the new settings.

See It in Action​

Follow this walkthrough in your app workspace:

  1. Open a saved app from Your Apps, then review its subjects and scan reports.
  2. Set up the recommendation catalog, import products, and test the returned recommendations.
  3. Configure SkinGPT and routines when you use those features.
  4. Review SDK Configuration, publish the changes, and test the saved preview.