> ## Documentation Index
> Fetch the complete documentation index at: https://zite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an app

> Learn about the various ways to get started such as writing effective prompts, selecting attachments, choosing integrations and more.

<img src="https://mintcdn.com/zite/ZFrnVWzRRHLYuyJY/help/images/how-to-build/starting-prompt-zite.webp?fit=max&auto=format&n=ZFrnVWzRRHLYuyJY&q=85&s=c017fe8ec2a6595795b98d05f3c3d8e5" alt="Zite starting prompt with App, Database, and Form options" style={{ width: "100%", aspectRatio: "16 / 9", display: "block", marginTop: 0, objectFit: "cover", borderRadius: "12px" }} width="3000" height="1688" data-path="help/images/how-to-build/starting-prompt-zite.webp" />

<Tip>
  Zite is best for internal tools, business apps, dashboards, portals, and workflows tied to existing data. It is not the best primary stack for launching a full SaaS product, though you can build external apps and add login when needed. Learn more in [What can I build?](/help/platform/getting-started/what-can-i-build).
</Tip>

## Getting started

<Steps>
  <Step>
    **Choose App**

    Start from `App` so Zite builds the user-facing experience. This is the right starting point for dashboards, portals, admin tools, approval queues, onboarding guides, and other business apps.
  </Step>

  <Step>
    **Select a data source via Integrations**

    Decide where the app should store or read data. For most new projects, start with [Zite Database](/help/database/overview). If your team already works from [Google Sheets](/help/integrations/google-sheets) or [Airtable](/help/integrations/airtable), connect that source instead.
  </Step>

  <Step>
    **Pick a brand or theme**

    If you have a [Brand Kit](/help/platform/how-to-build/brand-kit), select it before building so Zite can match your logo, colors, fonts, and guidelines. You can also create a new Brand Kit at this stage, or choose and change a [theme](/help/platform/how-to-build/design) later.
  </Step>

  <Step>
    **Choose Plan it or Build it**

    Use `Plan it` when the request is new, broad, or connected to multiple pages, roles, approvals, dashboards, or integrations. Use `Build it` when your first request is small and specific. Learn more in [Agent Modes](/help/platform/how-to-build/agent-modes/overview).
  </Step>

  <Step>
    **Submit a specific prompt**

    Include the app type, users, workflow, important views, and any login requirements. The more concrete your first prompt is, the better Zite can plan and build the first version.
  </Step>
</Steps>

## Popular data sources

| Data source                                           | Best for                                                                  |
| ----------------------------------------------------- | ------------------------------------------------------------------------- |
| [**Zite Database**](/help/database/overview)          | New apps where Zite should create and manage the data structure.          |
| [**Google Sheets**](/help/integrations/google-sheets) | Teams that already manage operational data in spreadsheets.               |
| [**Airtable**](/help/integrations/airtable)           | Structured business data that already lives in Airtable bases and tables. |

<Tip>
  If you are not sure, start with [**Zite Database**](/help/database/overview). You can still connect other tools later through [integrations](/help/integrations/overview).
</Tip>

## Agent modes

| Mode         | Use it when                                                                                                                                | What happens                                                                                                       |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| **Plan it**  | You are starting a new app, the scope is unclear, or the app needs multiple pages, roles, approvals, dashboards, portals, or integrations. | Zite creates a plan first so you can review and edit the scope, then see wireframes of the design before building. |
| **Build it** | You know exactly what you want and the first version is small or clearly defined.                                                          | Zite starts building the app right away, and may ask clarifying questions if it needs more information.            |

<Note>
  For a first project, **Plan it** is usually the better choice. It helps turn a broad idea into a clearer build plan before any app changes are made. You can compare all options in [Agent Modes](/help/platform/how-to-build/agent-modes/overview), and choose the right model in [Model Selection](/help/platform/basics/model-selection).
</Note>

## Write the starting prompt

A strong starting prompt usually includes the details below. If you are unsure how to scope the project, start with [Plan mode](/help/platform/how-to-build/agent-modes/plan-mode) so Zite can help clarify the requirements first.

* **The app type:** e.g. a dashboard, portal, or approval workflow
* **The users:** e.g. employees, managers, or clients
* **The workflow:** what users need to view, create, update, approve, assign, export, or submit
* **Access needs:** whether the app is internal, shared externally, or requires [login](/help/platform/access/authentication)

## Example prompts

**Employee onboarding guide**

```text theme={null}
Build an employee onboarding guide for new hires and HR managers.
Track employees, onboarding tasks, owners, due dates, and completion
status. Include a new hire view, an HR admin view, and task reminders.
```

**Inventory management template**

```text theme={null}
Build an inventory management app for the operations team. Track items,
suppliers, stock counts, locations, and reorder thresholds. Include a
dashboard, low-stock alerts, item update forms, and manager-only editing.
```

**Dashboard builder tutorial**

```text theme={null}
Build a business dashboard for team leads. Show revenue, pipeline
status, owner performance, and weekly changes. Include filters by region
and owner.
```

**Client portal setup guide**

```text theme={null}
Build a client portal for external clients to view project status,
files, invoices, and next steps. Add login so each client only sees
their own projects.
```

**Approval workflow examples**

```text theme={null}
Build an approval workflow for purchase requests. Track request, vendor,
amount, department, approver, and status fields. Include submitter and
approver views, email notifications, and an approval history.
```

## FAQs

<AccordionGroup>
  <Accordion title="Should I start with App or Database?">
    Start with `App` when you want Zite to build an interface first. Start with `Database` when the first goal is to create or organize the underlying data.
  </Accordion>

  <Accordion title="Can I connect existing data after the app is created?">
    Yes. You can connect or change data sources later, including a Zite Database, Google Sheets, Airtable, or other integrations.
  </Accordion>

  <Accordion title="When should I use Plan it?">
    Use `Plan it` for new projects, unclear scope, multi-page apps, dashboards, portals, approvals, or integrations.
  </Accordion>

  <Accordion title="Can an app be shared outside my team?">
    Yes. Zite apps can be external and can include login when needed, though Zite is best suited to business apps and internal tools.
  </Accordion>
</AccordionGroup>

<p className="zite-related-topics-heading">Related topics</p>

<div className="zite-related-topics">
  <a href="/help/platform/getting-started/what-can-i-build">What can I build?</a>
  <a href="/help/integrations/google-sheets">Build with Google Sheets</a>
  <a href="/help/integrations/airtable">Build with Airtable</a>
  <a href="/help/platform/how-to-build/brand-kit">Create a Brand Kit</a>
  <a href="/help/platform/basics/model-selection">Model Selection</a>
  <a href="/help/platform/how-to-build/agent-modes/overview">Agent Modes</a>
  <a href="/help/platform/access/authentication">Authentication</a>
</div>
