> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/analytics/create-an-app.md).
# Create your first app
In this tutorial you build a sales dashboard with KPI cards, a filter and four charts. It takes about ten minutes. The screenshots use the Floraya sample data, but you can follow along with any semantic model.
What you will build
{% hint style="info" %}
You need the **Analytics Creator** role and access to at least one [semantic model](/trulyp/data/semantic-modeling.md).
{% endhint %}
{% stepper %}
{% step %}
### Create the app
1. Go to **Analytics** and click **Create app** at the top right.
2. A new app called **Dashboard 1** (or **Dashboard 2**, and so on) opens in the editor.
3. Click the name at the top left and type a better one, for example **Sales overview**.
The editor has three areas: the toolbar at the top, the canvas on the left, and the panel with the tabs **Visuals**, **Edit visual**, **Data**, **Layers** and **Dashboard** on the right. See [The app editor](/trulyp/analytics/the-app-editor.md) for a full tour.
{% endstep %}
{% step %}
### Connect your data
A new app opens on the **Data** tab. Under **Available models** you see the semantic models you have access to.
Click **Connect** next to the model you want to use. It moves to **Connected**, and its fields appear in the **Fields** list next to it.
Don't have a semantic model for your data yet? You can also [import an Excel or CSV file](/trulyp/analytics/data-sources-and-fields.md#import-an-excel-or-csv-file).
{% endstep %}
{% step %}
### Add a KPI card
1. Open the **Visuals** tab and click **KPI Card**. The card appears on the canvas and the **Edit visual** tab opens.
2. Under **Value**, click **+ Choose field** and pick a measure, for example `net_sales`. The card shows the total.
3. Open the **Titles** tab and type a title, for example **Net sales**.
To show the value as currency, open the **Styling** tab, expand **Data labels**, set **Measure format** to **Currency**, enter a **Currency code** such as `EUR` and set **Decimal places** to `0`.
Repeat this for **Gross margin** and **Units sold**.
{% hint style="success" %}
**Tip:** you can also double-click a field in the **Fields** list (or select it and press **Enter**) to add it to the selected visual. Trulyp puts it in the first slot that fits.
{% endhint %}
{% endstep %}
{% step %}
### Add a filter
1. In the **Visuals** tab, scroll to **Dashboard Objects** and click **Filter**.
2. Set **Data source** to your model and **Dimension** to the field you want to filter on, for example `channel`.
3. Under **Filter target visuals**, tick every visual the filter should affect.
{% hint style="warning" %}
A new filter does not affect any visual until you tick them under **Filter target visuals**. Visuals you add later must be ticked too.
{% endhint %}
{% endstep %}
{% step %}
### Add charts
**A line chart over time**
1. Click **Line** in the **Visuals** tab.
2. Under **Category / X axis** choose a date field, for example `order_date`. Dates are grouped by year by default; change the grouping next to the field to **Month** (under **Continuous**) to see a monthly trend.
3. Under **Value / Y axis** choose `net_sales`.
**A bar chart and a donut**
* Add a **Bar** chart with `channel` on the X axis and `net_sales` as the value. On the **Options** tab, click **Horizontal** to turn it into a horizontal bar chart. On the **Styling** tab, switch on **Show value labels** under **Data labels**.
* Add a **Donut** with `primary_flower` as **Slice category** and `net_sales` as **Slice size**.
* Add a **Heatmap** with `day_of_week` as **X category**, `channel` as **Y category** and `quantity` as **Color value**.
See [Visuals](/trulyp/analytics/visuals.md) for every chart type and the fields it needs.
{% endstep %}
{% step %}
### Arrange the canvas
* **Move** a visual by dragging it.
* **Resize** it by dragging one of its edges or corners.
* Visuals snap to a grid of 48 columns and push each other out of the way, so they never overlap. If you want to place visuals on top of each other, switch to **Freeform** on the **Layers** tab.
{% endstep %}
{% step %}
### Save and preview
* Click **Save** (or press **Ctrl+S** / **Cmd+S**). Trulyp also saves automatically every two minutes, but only a manual save updates the thumbnail on the home page.
* Click **Preview** to see the app as your viewers will. Click **Edit** to return to the editor.
In view mode, try clicking a bar: the other visuals filter to that channel. See [Filters and interactivity](/trulyp/analytics/filters-and-interactivity.md).
{% endstep %}
{% step %}
### Share it
Click **Share** to copy a link, get an embed code or download a Tableau extension file, or use **…** > **Manage sharing** to give colleagues access. See [Sharing and embedding](/trulyp/analytics/sharing-and-embedding.md).
{% endstep %}
{% endstepper %}
### Next steps
* Add more pages with the **+** next to the page tabs, and link them with [buttons](/trulyp/analytics/visuals/dashboard-objects.md#button).
* Create [calculations](/trulyp/analytics/calculations.md) such as margin percentages or share of total.
* Change the look of the whole app in the [Dashboard settings](/trulyp/analytics/global-chart-options.md).
* Let [Vizzy AI](/trulyp/analytics/vizzy-ai-in-analytics.md) improve your dashboard even further!
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.infotopics.com/trulyp/analytics/create-an-app.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
