> For the complete documentation index, see [llms.txt](https://docs.lambahq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lambahq.com/getting-started/creating-your-first-app.md).

# Creating Your First App

{% hint style="info" %}
**Reasons for Using Apps:** Utilizing apps on Lamba enables you to divide your usage across multiple products you possess. You can designate one app specifically for your e-commerce platform and a separate app for your social media publishing or CRM product etc. 

Each app houses the logic, API keys, configurations and services for a particular product!
{% endhint %}

## Step 1 - Creating An App

Sign in to your Lamba Account, navigate to the **Apps** section and click on the **New App** button to create your first app, as shown in the screenshots below:

<div><figure><img src="/files/ZnLf7ag1DIa7IB0wplnv" alt=""><figcaption><p>Creating New App</p></figcaption></figure> <figure><img src="/files/v0ARFeCUWiY1y7YN1hlr" alt=""><figcaption><p>Viewing Your App Listings</p></figcaption></figure></div>

## Step 2 - Understanding Your App

After creating your app, you should see it in the list of apps you've created. Click on the **View** button to go to your app's details page.&#x20;

There, you should see something similar like the screenshot below:

<div><figure><img src="/files/ftHDszBxQiMt6J4CYtw1" alt=""><figcaption><p>Your app Information &#x26; Analytics page</p></figcaption></figure> <figure><img src="/files/9MnXkoStypBDk40kmNgG" alt=""><figcaption><p>Your app Customers/Users section</p></figcaption></figure></div>

Your app has two important sections outlined below:

{% tabs %}
{% tab title="Overview" %}
This is where you'll see the usage statistics of your app. This section also shows you the list of customers or users you've added to your app.

Lamba provides a platform for integrating users into your app, either through the Lamba dashboard or its API. This setup allows you to separate the resources utilized by each user within your application. For example, in a CRM product, each user (such as a company's admin) would typically provide their unique email configuration settings for sending emails. This separation of resources is particularly beneficial in such cases. Essentially, Lamba is designed to seamlessly integrate with your product, as demonstrated in the following structure:

{% code fullWidth="true" %}

```
// Your Product Model         |        // Your Lamba App
-- SellMart                   |        -- SellMart
   -- Users                   |           -- Users
      -- User1                |              -- User1
         -- id                |                 -- id (generated by lamba)
         -- name              |                 -- name (from your User1.name)
      -- User2                |                 -- customer_id (from your User1.id)
         -- id                |                 ...
         ...                  |                 ...
```

{% endcode %}

Now, each user in your Lamba app has its email, social media, meetings etc configurations.

In otherwords, you add each user in your product, to your lamba app (only when neccessary).&#x20;

Note that it is pointless adding a user in your product to your lamba app if they don't interact with lamba in any way. Only add the user when they need to interact with Lamba, in your product.
{% endtab %}

{% tab title="Settings" %}
This section is where you can update your app's preferences, generate API keys, manage services your app can interact with etc.
{% endtab %}
{% endtabs %}


---

# 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.lambahq.com/getting-started/creating-your-first-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.