> ## Documentation Index
> Fetch the complete documentation index at: https://docs.symplr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

Find answers to commonly encountered questions and issues when using Symplr. Use this page to quickly troubleshoot problems and find guidance before contacting support.

## Quick Start

<AccordionGroup>
  <Accordion title="What is Symplr used for?">
    Symplr is an AI-powered no-code platform that allows users to generate mobile and web applications using Figma designs, AI prompts, and reusable templates.
  </Accordion>

  <Accordion title="Do I need coding experience to use Symplr?">
    No. Symplr is designed for users without coding experience. The platform automatically generates application screens, navigation, and structure based on your input.
  </Accordion>

  <Accordion title="What type of applications can I build with Symplr?">
    Symplr allows you to generate mobile and web applications based on UI designs or AI prompts, including multi-screen apps with navigation and interactive components.
  </Accordion>

  <Accordion title="Is there a limit to the number of screens I can generate?">
    No. The number of screens depends on the complexity of your design or prompt. Larger designs may take longer to process.
  </Accordion>

  <Accordion title="Can I search for a project in Symplr?">
    Yes, Symplr allows you to quickly search for your projects using the search functionality available on the Home page.

    **Steps:**

    1. Navigate to the **Home** page after logging into the application
    2. Locate the **search bar** at the top of the **“Your Apps”** section
    3. Enter the name of the project you want to find
    4. Review the filtered results displayed below
    5. Click on the project to open it.

    Using the search feature helps you quickly locate specific projects, especially when you have multiple applications.
  </Accordion>

  <Accordion title="Can I delete a project?">
    Yes, you can delete a project directly from the **Home** page in Symplr.

    **Steps:**

    1. Navigate to the **Home** page after logging into the application
    2. Locate the project you want to delete in the **“Your Apps”** section
    3. Click on the **three-dot menu (⋮)** on the project card
    4. Select the **“Delete”** option from the menu
    5. Confirm the deletion if prompted.

    Once deleted, the project will be permanently removed from your workspace.
  </Accordion>
</AccordionGroup>

## Figma & AI Generation

<AccordionGroup>
  <Accordion title="How can I generate an application in Symplr?">
    You can generate an application in Symplr using either a Figma design or AI prompts, depending on your preference.

    * **Import a Figma File URL** - Provide a Figma file link to automatically convert your design into application screens and navigation.
    * **Use AI Prompts** - Describe your application using natural language prompts, and Symplr will generate the screens and structure based on your input.
    * **Use Templates** - Select from pre-built templates to quickly create an application, then customize it to match your requirements.

    All three approaches enable you to generate a fully functional application in minutes—giving you the flexibility to start from a design, an idea, or a ready-made foundation.
  </Accordion>

  <Accordion title="What happens after I import a Figma file or use AI prompts?">
    Symplr generates a **Blueprint View** that displays all screens, their structure, and navigation flow—allowing you to review and validate your application before proceeding further.
  </Accordion>

  <Accordion title="Can I update my design after importing it?">
    Yes. You can modify your Figma file and re-import it to regenerate an updated **Blueprint View**. See [Importing Figma Files](https://docs.101studio.co/untitled-page#importing-figma-files-into-symplr) for step-by-step instructions.
  </Accordion>

  <Accordion title="Can I modify my application after generating it using AI prompts?">
    You can modify your application after generating it using AI prompts.

    * Update your AI prompt and regenerate the application to reflect design or structural changes
    * Edit screens, navigation, and flows directly in the **Blueprint View**
    * Add new screens or update existing ones based on your requirements

    This flexibility allows you to iteratively refine your application without starting from scratch.
  </Accordion>

  <Accordion title="Which method should I use — Figma import or AI prompt?">
    The best method depends on whether you already have a design or want to create an application from scratch.

    * **Use Figma import** If you already have a Figma design, this option allows you to convert your existing UI screens into a functional application.
    * **Use AI prompts** If you do not have a design, you can describe your application using prompts, and Symplr will generate the screens and structure for you.
  </Accordion>

  <Accordion title="What happens if my Figma design is complex?">
    Complex designs may take longer to process, and some components may require adjustments to ensure accurate screen generation.
  </Accordion>
</AccordionGroup>

## Screens, Navigation & Workflows

<AccordionGroup>
  <Accordion title="What is the Blueprint View?">
    The **Blueprint View** is a visual representation of your application, showing all screens and their navigation connections.
  </Accordion>

  <Accordion title="Can I view individual screens in detail?">
    Yes, Symplr allows you to view and inspect each screen individually after the import process.

    **Steps:**

    1. Navigate to the **Blueprint View** after importing your design
    2. Click on the **Pages** tab from the main interface
    3. Locate the **Screens** panel, which lists all available screens
    4. Select a screen to view it in detail in the main display area
  </Accordion>

  <Accordion title="Can I edit screens directly in Symplr?">
    Yes. You can open individual screens in Symplr and make adjustments directly within the platform.

    **Steps:**

    1. Navigate to the **Blueprint View** after importing your design
    2. Click on the **Pages** tab from the main interface
    3. Locate the **Screens** panel, which lists all available screens
    4. Select the screen you want to edit
    5. Make the required modifications

    For more significant design changes, you can update your Figma file or AI prompt and regenerate the application to reflect those updates.
  </Accordion>

  <Accordion title="How is navigation between screens created?">
    Navigation is automatically generated based on the structure and relationships defined in your Figma design or AI prompt.

    You can also manually add or update navigation between screens directly from the **Blueprint View**, giving you full control over the application flow.
  </Accordion>

  <Accordion title="What should I do if navigation is incorrect?">
    If the navigation between screens is incorrect, you can update it directly from the **Blueprint View** or modify your source and regenerate the application.

    **Option 1: Update navigation in the Blueprint View**

    1. Navigate to the **Blueprint View** of your application
    2. Identify the screen where the navigation needs to be updated
    3. Click on the **(+) icon** on the screen card to add a new connection
    4. In the **“Add to Storyboard”** dialog, select **“Screen”**
    5. Choose the target screen from the list or create a new one
    6. Select the appropriate **event** (e.g., onPress, onLoad) to define when the navigation should trigger
    7. Save and verify the updated navigation flow

    **Option 2: Update the source and regenerate**

    If the issue is due to your design or prompt:

    * Update your **Figma file** (e.g., screen structure or navigation logic), or
    * Refine your **AI prompt** to better define the navigation flow

    After making changes:

    1. Re-import the Figma file or regenerate the application. See [Importing Figma Files](https://docs.101studio.co/untitled-page#importing-figma-files-into-symplr) for step-by-step instructions.
    2. Review the **Blueprint View** to confirm the navigation is correct
  </Accordion>

  <Accordion title="Can I add new screens to my application?">
    Yes, you can add new screens to your application directly from the **Blueprint View** and connect them to your existing flow.

    **Steps:**

    1. Navigate to the **Blueprint View** of your application
    2. Click on the **(+) icon** on the screen where you want to add a new connection
    3. In the **“Add to Storyboard”** dialog, select **“Screen”**
    4. Choose an existing screen or select **“Add Blank Screen”** to create a new one
    5. Select the appropriate **event** (e.g., onPress, onLoad) to define when the screen should be triggered
    6. Save and verify the updated flow.

    This allows you to extend your application by adding new screens and connecting them seamlessly.
  </Accordion>

  <Accordion title="Can I connect APIs to my application?">
    Yes. You can connect APIs to individual screens, enabling dynamic data handling and interactions within your application.
  </Accordion>

  <Accordion title="Can I configure workflows for screens?">
    Yes, you can configure workflows for screens directly from the **Blueprint View** to define actions such as API calls and backend logic.

    **Steps:**

    1. Navigate to the **Blueprint View** of your application
    2. Click on the **(+) icon** on the screen where you want to add a workflow
    3. In the **“Add to Storyboard”** dialog, select **“Workflow”**
    4. In the **Add Workflow** screen, switch to the **“Workflow Catalogue”** tab
    5. Search for an existing workflow or choose one from the list
    6. Select the workflow and add it to your screen.

    Once added, the workflow will be connected to the screen and can be used to handle actions such as API calls and data processing.
  </Accordion>

  <Accordion title="Can I manage APIs and workflows for each screen separately?">
    Yes. Symplr allows you to configure APIs and workflows at the screen level, giving you flexibility to manage functionality for each screen independently.
  </Accordion>

  <Accordion title="What do the rectangles in Blueprint View represent?">
    Each rectangle within Blueprint View represents an individual application screen.

    Screens are connected using navigation paths that represent how users move through the application during runtime.
  </Accordion>

  <Accordion title="What do the navigation connectors mean?">
    Navigation connectors represent the flow between screens and interactions within the application.

    Connector labels such as `onPress` help identify the interaction or action that triggers the navigation flow between connected screens.
  </Accordion>

  <Accordion title="Can I duplicate screens in Blueprint View?">
    Yes. Screen management options are available from the three-dot menu on each screen card.

    Available actions include:

    * Rename
    * Duplicate
    * Delete
      These options help organize and maintain the application structure within Blueprint View.
  </Accordion>

  <Accordion title="What are Decisions in Blueprint View?">
    Decisions are used to create conditional or branching navigation paths within the application flow.

    They help define multiple outcomes based on user actions, validations, or application conditions.
  </Accordion>

  <Accordion title="What are User Journeys in Blueprint View?">
    User Journeys represent reusable interaction flows and connected application experiences within the blueprint structure.

    They help organize larger navigation patterns and reusable user interaction sequences across the application.
  </Accordion>

  <Accordion title="Can I rename screens in Blueprint View?">
    Yes. Screen names can be updated directly from the three-dot menu available on each screen card within Blueprint View.

    Renaming screens helps improve organization and readability within larger application structures.
  </Accordion>

  <Accordion title="Can I delete screens from Blueprint View?">
    Yes. Screens can be removed from the application structure using the **Delete** option available from the three-dot menu on the screen card.

    Deleting unused screens helps maintain a cleaner and more organized application flow.
  </Accordion>
</AccordionGroup>

## Build, Run & Test

<AccordionGroup>
  <Accordion title="Can I build and run the application within Symplr?">
    Yes, you can build and run your application directly within Symplr without needing a local setup.

    **Steps:**

    1. Navigate to the **Blueprint View** of your application
    2. Click on the **Build & Run App** icon in the top-right corner
    3. In the panel, click **Build** under **Build & Run New App** to start the build process
    4. Wait for the build to complete

    Once the build is successful, the application will run within the Symplr environment.

    You can also use the **Load** option under **Load Latest App** to quickly run the most recent build.
  </Accordion>

  <Accordion title="Can I run the application on my mobile device?">
    Yes, you can run your application on a mobile device using the **Expo Go** (a mobile app used to run your application).

    **Steps:**

    1. Navigate to the **Blueprint View** of your application
    2. Click on the **“Run App on Your Device”** icon in the top-right corner
    3. A **QR code** will be generated for your application
    4. Install the **Expo Go** on your mobile device (if not already installed)
    5. Open Expo Go and scan the QR code
    6. The application will load and run on your device. This allows you to test your application on a real device and verify its behavior before deployment.
  </Accordion>

  <Accordion title="What happens if the build fails?">
    An error message will be displayed indicating the cause of the failure. Build failures may occur due to configuration issues or unsupported elements. Review your setup and try rebuilding the application.
  </Accordion>

  <Accordion title="Can I download the generated code?">
    Yes, Symplr allows you to download the generated application code for use in your local development environment.

    **Steps:**

    1. Navigate to the **Blueprint View** of your application
    2. Click on **Developer Tools** icon in the top-right corner
    3. Enable the **“Generate Test Cases”** toggle (optional, if you want to include automated tests)
    4. Locate the **“Download Code”** section in the panel
    5. Click **“Download”** to request the generated code
    6. The generated code will be sent to your registered email address
    7. Open the email and download the code package. Once downloaded, you can extract the files and run the application locally using your preferred development setup.
  </Accordion>

  <Accordion title="Where do I receive the generated code package?">
    After the code generation process completes successfully, Symplr delivers the generated application package to your registered email address.

    The email includes a **Download Code** button used to download the compressed source package to your local machine.
  </Accordion>

  <Accordion title="What is included in the generated code package?">
    The generated application package contains the application source files based on the configured screens, workflows, widgets, navigation, and application settings defined within the project.

    Depending on the selected generation options, the package may also include:

    * Generated test resources
    * Security-related configurations
    * Workflow implementations
    * Application assets and configurations
  </Accordion>

  <Accordion title="Does Symplr support automated testing?">
    Yes. Symplr can generate automated test cases for your application, allowing you to validate functionality and ensure the application works as expected.
  </Accordion>

  <Accordion title="How can I test my application?">
    You can test your application in Symplr using multiple methods, depending on your testing needs.

    * **Run within Symplr** - Build and run the application directly in the platform to quickly verify screens, navigation, and functionality.
    * **Run on a mobile device** - Use the **Expo Go** to scan the QR code and test the application on a real device.
    * **Run locally using downloaded code** - Download the generated code, run it in an emulator, and execute automated test cases for more advanced testing. Choose the method that best fits your testing scenario—from quick validation to full testing with automation.
  </Accordion>

  <Accordion title="Can I modify the downloaded code?">
    Yes. The generated code can be edited and customized in your local development environment.
  </Accordion>

  <Accordion title="What is included in the downloaded code package?">
    The downloaded package includes the complete application source code along with generated test cases, allowing you to run, modify, and extend the application in your local development environment.
  </Accordion>

  <Accordion title="Can I run the application without downloading the code?">
    Yes. You can run the application directly within Symplr or on your device using Expo Go.

    **Options:**

    * **Run within Symplr** - Build and run your application directly inside the platform to quickly test functionality and user flows.
    * **Run on your device using Expo Go** - Launch the application on your mobile device by scanning the QR code using the **Expo Go**.

    These options allow you to validate your application quickly before downloading or deploying the code. For step-by-step instructions, see [Build & Run the Application](https://docs.101studio.co/caffd#build-&-run-your-application-instantly).
  </Accordion>

  <Accordion title="Can I rebuild my application after making changes?">
    Yes. After updating screens, workflows, layouts, or application configurations, you can rebuild the application from the **Build & Run** menu.

    To rebuild the application:

    1. Open the **Build & Run** menu
    2. Click **Build**
    3. Wait for the updated preview to generate

    Symplr generates a new application preview using the latest project configuration.
  </Accordion>

  <Accordion title="Do I need to download the code to test my application?">
    No. Symplr allows applications to be built, previewed, and tested directly within the platform without downloading the generated source code.

    You can:

    * Preview the application in the browser
    * Validate screens and workflows
    * Test layouts and interactions
    * Run the application on a physical device using Expo Go

    Downloading the code is only required for external development or deployment workflows.
  </Accordion>
</AccordionGroup>

## Customization & Performance

<AccordionGroup>
  <Accordion title="Can I apply themes to my application?">
    Yes, Symplr allows you to apply and customize themes to control the look and feel of your application.

    **Steps:**

    1. Navigate to the **Theme** section from the left-hand menu
    2. Select **“Tokens”** or another category (e.g., Color, Typography, Shadow)
    3. View or edit existing theme values such as colors, borders, etc.
    4. Click the **“+ Add”** button to create new theme tokens if needed
    5. Choose the appropriate type (e.g., Color, Number, String, Boolean)
    6. Update the values to match your desired design. Once configured, the theme settings will be applied across your application to ensure a consistent visual style.
  </Accordion>

  <Accordion title="Can I change the theme after creating the project?">
    Yes. You can update the theme at any time, and the changes will be applied across your application.
  </Accordion>

  <Accordion title="How long does it take to generate an application?">
    It typically takes a few minutes, depending on the complexity of the design, number of screens, and application structure.
  </Accordion>

  <Accordion title="Does Symplr support large or complex projects?">
    Yes, but complex designs may require additional time and proper structuring for best results.
  </Accordion>

  <Accordion title="Can I customize application themes and styles?">
    Yes. Symplr allows application-wide themes and reusable design settings to be configured from the **Theme** section.

    You can customize:

    * Colors
    * Typography
    * Spacing
    * Borders
    * Radius values
    * Shadow settings
    * Reusable design tokens

    These settings help maintain visual consistency across the application.
  </Accordion>
</AccordionGroup>

## Account & Projects

<AccordionGroup>
  <Accordion title="Do I need to log in to use Symplr?">
    Yes. A valid Symplr account is required to import designs and generate applications.
  </Accordion>

  <Accordion title="Can I access my projects later?">
    Yes. Your projects are saved and can be accessed from your Symplr dashboard.

    **Steps:**

    1. Navigate to the **Home** page after logging into the application
    2. Locate the **“Your Apps”** section, where all your created projects are listed
    3. Browse through the list to find your project
    4. Click on the project name or the **Open** button to continue working on it. You can also use the **search bar** to quickly find a specific project by entering its name.
  </Accordion>

  <Accordion title="Can I share my project with other users?">
    Yes. Symplr allows you to share projects directly from the **Blueprint View** for collaborative editing and review.

    **Steps:**

    1. Open the project in **Blueprint View**
    2. Click the **Share** button in the top-right corner
    3. Enter the recipient’s email address
    4. Click **Invite**

    The invited user will receive an email invitation with access to the shared project.
  </Accordion>

  <Accordion title="What happens after I share a project?">
    After a project is shared, the invited user receives an email invitation containing access to the project.

    Once the invitation is accepted and the user signs in to Symplr, the shared project opens directly in **Blueprint View** for continued collaboration and application development.
  </Accordion>

  <Accordion title="Why can’t the invited user see the shared project?">
    If the shared project is not visible after accepting the invitation:

    * Verify the correct email account was used
    * Refresh the dashboard
    * Confirm the invitation was accepted successfully
    * Ask the project owner to resend the invitation if required

    Shared projects are available from the **Your Apps** section in the Symplr dashboard.
  </Accordion>

  <Accordion title="Can I reopen previously shared projects?">
    Yes. Shared projects remain available from the **Your Apps** section in the Symplr dashboard.

    To reopen a shared project:

    1. Sign in to Symplr
    2. Open the dashboard
    3. Locate the shared project card
    4. Click **Open**

    The project opens directly in **Blueprint View** for continued collaboration and editing.
  </Accordion>
</AccordionGroup>

## Troubleshooting & Support

<AccordionGroup>
  <Accordion title="Why are some screens missing after import?">
    This may occur if certain parts of your Figma design are not structured in a way that Symplr can recognize as screens.

    Common reasons include:

    * Screens are not defined using **frames**
    * Frames are nested incorrectly or grouped instead of structured as screens
    * Inconsistent or unclear naming of screens
    * Screens placed outside the main page structure

    To ensure all screens are imported correctly:

    * Use **frames** to represent each screen
    * Ensure each screen is clearly named and organized
    * Avoid grouping screens inside other frames unnecessarily
    * Keep screens structured at a consistent hierarchy level

    After making these updates:

    * Update your Figma file
    * Re-import it into Symplr to regenerate the Blueprint View. See [Importing Figma Files](https://docs.101studio.co/untitled-page#importing-figma-files-into-symplr) for step-by-step instructions.
  </Accordion>

  <Accordion title="Why is my application not running on my device?">
    If your application is not running on your mobile device, it is usually due to connectivity or setup issues.

    **Ensure the following:**

    * Your **mobile device and system are connected to the same network**
    * The **Expo Go** is installed and up to date
    * The **QR code is scanned correctly** using Expo Go
    * The application has been successfully built before attempting to run it. If the issue persists, try regenerating the QR code and scanning it again.
  </Accordion>

  <Accordion title="Why does my design look different in Symplr?">
    Differences may occur if certain design elements in your Figma file are not fully supported or are structured in a way that affects how they are interpreted by Symplr.

    Common reasons include:

    * Use of unsupported or complex components
    * Deeply nested groups or layers
    * Missing or inconsistent Auto Layout configurations
    * Differences in spacing, alignment, or constraints

    To improve design accuracy:

    * Structure screens using clear **frames**
    * Simplify deeply nested groups and layers
    * Use standard and reusable components where possible
  </Accordion>

  <Accordion title="Why are some components not generated correctly?">
    This may occur if the components in your Figma design are not structured in a way that can be accurately interpreted by Symplr.

    Common causes include:

    * Deeply nested layers or groups
    * Use of unsupported or complex components
    * Inconsistent or unclear structure within frames

    To improve accuracy:

    * Simplify your design by reducing deeply nested groups
    * Use **frames** to clearly define screens
    * Ensure components are properly organized and reusable
    * Avoid unsupported or overly complex elements where possible

    After making these updates:

    * Update your Figma file
    * Re-import it into Symplr to regenerate the application. See [Importing Figma Files](https://docs.101studio.co/untitled-page#importing-figma-files-into-symplr) for step-by-step instructions.
  </Accordion>

  <Accordion title="Why is my QR code not working?">
    If the QR code is not working, it is usually due to connectivity or session-related issues.

    **Ensure the following:**

    * Your **mobile device and system are connected to the same network**
    * The **Expo Go** application is installed and up to date
    * The **QR code is active and has not expired**
    * The QR code is scanned correctly using the **Expo Go**.

    **If the issue persists:**

    * Regenerate the QR code and try scanning again
    * Refresh the application in Symplr and reopen the QR code
  </Accordion>

  <Accordion title="How do I contact support?">
    You can contact the Symplr support team using the following options:

    * **Report issues directly from the application (Contact Support)** When an error occurs, click the **“Contact Support”** button displayed with the error message to submit the issue instantly.
    * **Use the Help button** Click the **Help** button within the application to start a chat for general questions or guidance.
    * **Email support** Send an email to [**support@101digital.io**](mailto:support@101digital.io) for detailed issues or when you need to share attachments. Choose the option that best fits your situation for faster assistance.
  </Accordion>

  <Accordion title="What information should I provide when contacting support?">
    To help the support team investigate and resolve your issue efficiently, include the following details:

    * Project / App Name
    * Description of the issue
    * Steps to reproduce
    * Screenshots or recordings (if applicable).

    Providing complete and accurate information helps speed up the troubleshooting process and ensures a quicker response.
  </Accordion>
</AccordionGroup>

## **Need More Help?**

If your question isn’t covered here, you can:

* Visit the **Contact Support** page
* Explore product documentation for detailed guides