# Building your App

It's time to begin building your first application! This section provides a structured guide to help you move from concept to a fully functional app—efficiently and effectively.

{% embed url="<https://www.youtube.com/watch?v=yfjvuff5y3s>" %}

***

### Step 1: Assign a Meaningful Name to Your App

Naming your application thoughtfully enhances usability and recognition. Choose a name that reflects the app’s function or domain to improve clarity for both developers and end users.\
Start by giving your app a meaningful name and project icon.

<figure><img src="/files/fAxvu1MhDdQxIdlRwhYc" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
*Example: Instead of “App\_001”, consider a descriptive name like “Inventory Tracker” or “Order Manager”.*
{% endhint %}

***

### Step 2: Define Your App Idea

Before initiating any project, clearly articulate your application’s purpose. The precision of your vision directly influences the quality of the output generated by eMOBIQ AI.

<details>

<summary>Lack of ideas?</summary>

*Click `Advanced Ideation` to help you clearly define what your app should do. The more specific you are, the better eMOBIQ AI can assist you to build your app*

<figure><img src="/files/QKNid1507FWwcYWGHC66" alt="" width="375"><figcaption></figcaption></figure>

</details>

<details>

<summary>Templated Projects</summary>

*If you are unsure what app to build, click on `Use suggested templates` to try using one of our templates to get started!*

<figure><img src="/files/EsdBK5qA44BrEMy1LAiD" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="warning" %}
*Do note that creating a templated app will consume credits.*
{% endhint %}

</details>

{% hint style="info" %}
*For more information on how to have a better App upon generation, refer to our* [*Advanced Prompting Guide*](/emobiq-ai/readme/building-your-app/advanced-prompting-for-app-creation.md)
{% endhint %}

***

### Step 3: Select Your Backend Service

Based on your objectives, select the appropriate application type. Each option is designed for a specific use case and technical architecture:

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

{% tabs fullWidth="false" %}
{% tab title="Stand-alone" %}

* Designed for UI-only prototypes or personal tools
* No backend database required
* Data is stored locally within the browser
  {% endtab %}

{% tab title="External API" %}

* Integrates with external systems such as Microsoft Business Central, Acumatica, Sage and many more!
* Requires pre-defined and accessible API endpoints
* Enables seamless connectivity with existing business ecosystems
* Full guide on[ External API configuration](/emobiq-ai/readme/external-api.md)

{% hint style="info" %}
*📝 Note: Ensure all external API function calls are documented and tested before selecting this mode.*
{% endhint %}
{% endtab %}

{% tab title="Summary" %}

<table><thead><tr><th width="149.76043701171875">App Type</th><th width="298.51806640625">Database Provisioning</th><th>Integration Capabilities</th></tr></thead><tbody><tr><td>Standalone</td><td>None - Local Storage</td><td>NA</td></tr><tr><td>External API</td><td>Leverages external databases via Function API</td><td>Custom integrations supported</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

### Step 4: Choose Between Autopilot or Manual Review Workflow

Decide how much oversight you want during the development lifecycle.

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

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><p>Autopilot</p><ul><li>Provides End-to-End Automation</li><li>No need for intermediate reviews</li><li>Best suited for trusted workflows or simple applications</li></ul></td><td></td></tr><tr><td><p>Manual Review</p><ul><li>Allows for feedback and adjustments at each stage before proceeding to the next</li><li>Increases control and accuracy, particularly for complex logic or design</li><li>Slightly higher cost due to increased AI interaction</li></ul></td><td></td></tr><tr><td><p>Docs &#x26; UI only</p><ul><li>Describe your UI needs in natural language</li><li>eMOBIQ AI generates the frontend and documentation</li><li>Preview and review the output</li><li>Export or refine as needed before moving to full implementation</li></ul></td><td></td></tr><tr><td></td><td></td></tr></tbody></table>

***

### Step 5: Allocate Budget

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

{% hint style="success" %}
*💰 Budget Tip: It is recommended to allocate 20 to 60 Credits per project depending on your application size. This is to account for prompt-based costs, especially when using **manual review**. For more information regarding costs you may refer to our* [*Pricing Guide*](/emobiq-ai/readme/how-pricing-works-in-emobiq-ai.md)*.*
{% endhint %}

***

### You’re Ready to Create!

With these steps completed, you now have a clear roadmap for developing your first eMOBIQ AI-powered app. Whether you're building a prototype or a full-scale enterprise solution, eMOBIQ AI empowers you to bring your vision to life quickly, intelligently, and with precision. Let’s discover what your new app can do!


---

# Agent Instructions: 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.emobiq.com/emobiq-ai/readme/building-your-app.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.