> For the complete documentation index, see [llms.txt](https://docs.quantumbyte.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quantumbyte.ai/home/quantumbyte-v2.0/readme.md).

# Getting Started

## Concept

<figure><img src="/files/1GlLY7h9frw5eLKXSRAj" alt="" width="563"><figcaption></figcaption></figure>

The concept of QuantumByte is a SuperApp, consisting of a **Main App** and multiple **Mini Apps**, developed or integrated using the available features within the QuantumByte Platform.

Each Mini App Developer will receive an account on the QuantumByte Platform, allowing them to either create new services or integrate existing ones into the Main App (Web Portal & Mobile Portal).

The QuantumByte ecosystem enables developers to build services directly within the Main App portal. This approach ensures that only one unified application appears to the public while offering multiple services developed independently by different developers—reducing the need for many separate public apps.

<div data-full-width="false"><figure><img src="https://github.com/QTN-DEV/quantumbyte-doc/blob/main/.gitbook/assets/New%20Project%20(2).png" alt="" width="563"><figcaption></figcaption></figure> <figure><img src="/files/YIf6pPJenXl0G5gdHZ4f" alt="" width="563"><figcaption><p>Mobile App Created with QuantumByte</p></figcaption></figure></div>

## Main Features

<figure><img src="/files/d1qNluF0PXiyfo4pneFh" alt=""><figcaption></figcaption></figure>

The INA Digital Platform uses our framework and offers several types of development tools that make it easier to integrate new applications or existing ones, as follows:

**Builder (Frontend)**\
This feature is used to create native services within the Mobile App and National Web Portal, as well as dashboard pages for managing services from the back-office side. It uses a drag-and-drop interface with standardized components.

**Package (Frontend)**\
This package/plugin feature is used to build native services within the Mobile App and National Web Portal using code templates. In this method, you create a plugin that will be merged into the Main App’s source code and compiled together.

**Microsite (Frontend)**\
This feature is used to create webview-based services within the Mobile App and National Web Portal using code templates, UI Kit components, and SDK libraries provided as service standards.

**Microservice (Backend)**\
This feature allows you to build backend services using available framework templates. It’s useful for developers who don’t yet have infrastructure or who want to leverage the stability of backend services running on the framework’s server cluster.

**Storage (Backend)**\
This feature is used to store document files within the framework. It can be utilized by those who don’t yet have infrastructure or who want to leverage the stability of the framework’s storage cluster.

**Database (Backend)**\
This feature allows you to create a database on the server for storing data within the framework.

**API Management**\
This feature enables data sharing via APIs through the framework.

***

## Frontend Service

These are recommendations for choosing the appropriate type of frontend, along with their advantages and disadvantages. You may use two different frontend types for the Main App Portal: one for the Mobile version and another for the Web version.

| Frontend Service | Description                                                                 | Advantages                                                                                                                                                                                                                                                                                                                                            | Disadvantages                                                                                                                                                                                                                              |
| ---------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Builder          | Suitable for services with simple, form-based UI/UX.                        | <p>Good performance (native) except when using webview widgets.<br><br></p><p>Allows you to quickly build services using drag-and-drop widgets.<br><br></p><p>Automatically generates both Mobile App and Web App frontends.<br><br></p><p>No need to update the Main App when changes are made.</p><p><br></p>                                       | <p>Limited widget options.<br><br></p><p>UI/UX customization is restricted and may not fit specific design needs.<br><br></p><p>Cannot install external dependencies.<br><br></p><p>Typically used for form-based services.</p><p><br></p> |
| Package          | Suitable for services with complex UI/UX and high performance requirements. | <p>Services can be developed using fully native code (Base Plugin).<br><br></p><p>UI/UX can be fully customized to match specific design or functional needs.<br><br></p><p>Delivers high native performance.<br><br></p><p>Allows installation of external dependencies.</p><p><br></p>                                                              | <p>Requires an app update whenever changes are made.<br><br></p><p>The Mobile App and Web App packages are separate, meaning developers must build each one individually.</p><p><br></p>                                                   |
| Microsite        | Suitable for services with complex UI/UX requirements.                      | <p>Services can be developed using full web-based code.<br><br></p><p>No need to update the Main App when changes are made.<br><br></p><p>UI/UX can be fully customized according to needs.<br><br></p><p>Automatically generates both Mobile App and Web App frontends.<br><br></p><p>Supports installation of external dependencies.</p><p><br></p> | <p>Lower performance compared to native solutions (runs via WebView).<br><br></p><p><br></p>                                                                                                                                               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.quantumbyte.ai/home/quantumbyte-v2.0/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.