iDIY'A

1st Step – Application Detail

This is the first step in setting up your application. Here, users specify whether they want to create a brand-new application or add a new module to an existing one. This foundational step ensures that the rest of the configuration process is tailored to the selected application type. The interface provides a friendly assistant message to guide users through the initial choices, making it easy for both beginners and experienced users to start their journey confidently.

  1. New Application: Begin creating a new, standalone application.
    1. Application Name: The name of the application as displayed in the UI and browser.
    2. Themes: Predefined or custom visual styles applied to the application's interface.
    3. Roles: User roles that determine access levels and permissions within the application.
    4. Upload Logo: Allows uploading a logo to represent the application visually.
    5. Description: A brief summary explaining the purpose or functionality of the application.
  2. New Module: Add functionality to an existing application as a module.
    1. Application: Refers to the specific app being configured or managed within the platform.
    2. Data Source: The backend source (e.g., API, database) from which the application retrieves or manages data.

2nd Step – Choose Builder Options

In this step, users select how they want to build their application by choosing from multiple builder options.

  1. AI Assisted Builder: Uses AI to help automatically generate application components based on user input or intent.
  2. API Payload First: Begins application design by defining the API response structure and mapping UI accordingly.
  3. Database-First Magic: Automatically generates application structure and UI by introspecting the database schema.
  4. Marketplace: Offers prebuilt templates, components, or integrations that can be used to accelerate application development.

3rd Step – Customize Application UI/UX

In this step, users personalize the look and feel of their application by configuring the user interface and experience. They can define entities such as forms, assign roles, choose a menu icon, and select a preferred form layout—Standard, Tab, or Form Wizard—to best suit their workflow. The intuitive design assistant guides users through each configuration phase, ensuring that the application’s interface is both functional and user-friendly.

4th Step – Configure Data Source

In this final step, users select the appropriate data source to power their application. Options include AI, HTTP, Workflow, NoSQL, and RDBMS, each tailored to different backend needs and architectures. This configuration step ensures that the application connects seamlessly to the necessary data services for optimal performance. Users can also opt to save their setup as a template for future reuse before finalizing the build by clicking “Submit.”

  1. AI: You will need to provide following information to connect a database using AI option
    1. Access Key: A secure token used to authenticate and authorize access to the model or API service.
    2. Model Name: The name of the AI or data model being integrated with the application.
    3. End Point: The URL where the application sends requests to access the model or service.
    4. Connection Name: A user-defined label for identifying and managing the model or API connection.
    5. Upload Logo: Allows adding a custom logo for visual representation of the model or integration.
    6. Description: A brief explanation of the model's purpose or the integration's function.
  2. HTTP: You will need to provide following information to connect a database using HTTP option
    1. Enable Swagger?: Enables integration using a Swagger (OpenAPI) specification for API documentation and interaction.
      1. Upload Swagger File: Upload a Swagger/OpenAPI JSON or YAML file to
      auto-generate endpoints and schemas.
    2. Base URL: The root URL where the API is hosted and accessible.
    3. Authentication: Method of securing API access (e.g., API key, OAuth, Basic Auth).
    4. Connection Name: A custom name to identify and reference this API connection.
    5. Upload Logo: Option to upload a logo for branding the API connection interface.
    6. Description: A short summary explaining the purpose or functionality of the API connection.
  3. Workflow: You will need to provide following information to connect a database using Workflow option
    1. Azure Subscription: The specific Azure account subscription under which resources are managed and billed.
    2. Resource Group: A container in Azure that holds related resources like function apps, storage, and databases.
    3. Function Apps: Azure-hosted serverless applications that contain functions triggered by events or HTTP calls.
    4. Connection Name: A custom label to identify and reference the Azure Function connection.
    5. Upload Logo: Option to upload a logo for visual branding of the Azure connection.
    6. Description: A brief summary describing the purpose or use case of the Azure Function integration.
  4. No SQL: You will need to provide following information to connect a database using No SQL option
    1. Database Account: The name or ID of your Cosmos DB account used to access the database services.
    2. Database: The specific database within the Cosmos DB account to connect to.
    3. Collection: A container within the database where documents or records are stored (also known as a container in newer terminology).
    4. Partition Key: A field used to logically partition data for performance and scalability within Cosmos DB.
    5. Access Key (Primary Key): The primary key used to authenticate and authorize access to the Cosmos DB account.
    6. Enable Azure Function: Allows triggering or integration with Azure Functions for serverless compute tasks.
    7. Connection Name: A user-defined label to identify this Cosmos DB connection.
    8. Upload Logo: Option to upload a logo to visually represent this database connection.
    9. Description: A brief description of the Cosmos DB connection and its intended use.
  5. RDMS: You will need to provide following information to connect a database using MS SQL option
    1. Server Name: The hostname or IP address of the server hosting the SQL database.
    2. Database: The specific database name to connect to on the server.
    3. User Name: The username used to authenticate with the database server.
    4. Password: The password associated with the database username for authentication.
    5. Port: The network port used to establish the connection to the database (commonly 1433 for SQL Server, 3306 for MySQL).
    6. Connection Name: A custom label to identify and reference this database connection.
    7. Upload Logo: Option to upload a logo for branding the connection interface.
    8. Description: A brief summary explaining the purpose or usage of this SQL database connection.