> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/additional-resources/adalo-app-academy/introduction-to-apps.md).

# Introduction to Apps

Everything you need to know about the mobile app world to help you get started.

### I Want To Make An App: What Kind of Apps Should I Make?

{% tabs %}
{% tab title="Course Details" %}
<https://appacademy.adalo.com/course/what-kind-of-app-make>

Take a behind-the-scenes look at how David Adkin, CEO of Adalo, decides what apps to make.
{% endtab %}
{% endtabs %}

### The No-Code Landscape

{% tabs %}
{% tab title="Course Details" %}
<https://appacademy.adalo.com/course/no-code-101-with-ben-tossell-founder-of-makerpad>

An introduction to the no-code landscape.
{% endtab %}
{% endtabs %}

### The Future Is No-Code: Picking Up The Skillset of the Future

{% tabs %}
{% tab title="Course Details" %}
<https://appacademy.adalo.com/course/the-future-is-no-code>

This project started with one simple idea. What if we could ask a bunch of experts the same questions to help us figure out what exactly “No-Code” is, how it’s going to impact everyone, and why we’re all so excited about it.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.adalo.com/additional-resources/adalo-app-academy/introduction-to-apps.md?ask=<question>&goal=<user_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.