> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/features/installing-the-pwa.md).

# Installing the Proliquid app

Install Proliquid as a full-screen app on a phone

Proliquid can be installed as a full-screen app on supported mobile browsers.

## Install from the prompt

When the install suggestion appears, choose **Install** or **Add app**. The installed app opens Proliquid without the normal browser controls.

On iPhone or iPad:

1. Open Proliquid in Safari.
2. Tap Share.
3. Choose **Add to Home Screen**.
4. Open Proliquid from the new Home Screen icon.

The mobile experience opens on Charts first. You can switch to News, Terminal, Screener, or More from the bottom navigation.

## Updates

Proliquid prepares application updates before reloading so the installed app and browser session use the same version.

If an update cannot start, check your connection and choose **Retry update**. If another Proliquid tab or app window is open, close it and try again.

The installed app improves access to the interface. It does not make exchange data or order placement available while the relevant connection is offline.

Related pages: [Mobile app](/features/mobile-app.md), [Link desktop to mobile](/getting-started/linking-desktop-to-mobile.md), [Footer](/features/footer.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 by asking a question.

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

```
GET https://docs.proliquid.xyz/features/installing-the-pwa.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.