> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/app-features-and-settings/remove-bottom-bar.md).

# Remove bottom bar

### How to open the app in full screen without bottom navigation?

<figure><img src="https://3330324049-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxUo90vXzDtbgOtaUaLYv%2Fuploads%2FJqvaNYxs4K7oOkKthvoL%2FBottom%20bar%20removal.png?alt=media&amp;token=3b96265c-8248-4dbf-84a5-e05eeb9fba64" alt=""><figcaption></figcaption></figure>

If you want your app to open in full screen without showing the bottom navigation bar, you can configure this from the Navigation section.

Step 1: Disable the bottom bar completely

* Go to [**Navigation > Bottom bar**](https://app.appmysite.com/app/bottom-bar) tab.
* Disable the "Enable bottom bar" toggle.

This will remove the bottom navigation from your app interface.

Step 2: Set a specific screen as the home screen

Use the side menu instead of the bottom bar to define which screen opens first.

* Go to [**Navigation > Menu**](https://app.appmysite.com/app/menu).
* Expand the menu item you want users to see first.
* Enable the Set as home screen checkbox under that item.

This will ensure the selected screen opens when users launch the app and the app will open in full screen without a bottom bar navigation.&#x20;


---

# 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.appmysite.com/frequently-asked-questions/app-features-and-settings/remove-bottom-bar.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.
