> For the complete documentation index, see [llms.txt](https://4wsplatform.gitbook.io/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4wsplatform.gitbook.io/user-guide/best-practises.md).

# Best practises

In this section you can find helpful tips to follow when defining your application.

An application is composed of a database and metadata defined through the configuration process, using the App Designer.

The next sections describe these two tasks:

* how to **design and maintain a database**
* how to **design the most common functionalities**

The design and maintenance of a database passes through a set of rules to follow, in order to create an effective database, including rules about the naming of database fields and the supported database types.

The design of common functionalities using the App Designer are split up in two sections:

* [Use cases for Web Applications](/user-guide/best-practises/2-3-creating-a-web-app-common-use-cases.md)
* [Use cases for Mobile Applications](/user-guide/best-practises/2-4-creating-a-mobile-app-common-use-cases.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://4wsplatform.gitbook.io/user-guide/best-practises.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.