> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/how-to/add-meltingspot-to-your-phone-computer-home-screen.md).

# Add MeltingSpot to your phone/computer home screen

Get quick access to MeltingSpot by adding a shortcut within your applications on your phone or your computer.

{% tabs %}
{% tab title="iPhone & iPad" %}

1. Open your Spot on Safari.
2. Tap the `Share` icon on the bottom of the page.
3. Scroll down and click on `Add to Home Screen`.
4. Choose a name for the shortcut. We recommend you to write your Spot name or "MeltingSpot". Click `Done`.
5. Close safari, and find MeltingSpot icon within your applications on your home screen.
6. Access your Spot by clicking on the new Favicon. It will open on a dependent navigation window (just *like* an application).

{% embed url="<https://www.loom.com/share/b98c4ce6ff7948c88bef1c91e5e1bcd0?sid=fc9578b9-5321-4a15-bcb8-9273d5d578c3>" %}
{% endtab %}

{% tab title="Mac" %}

1. Open your Spot on Safari.
2. Tap the `Share` icon on the top-right side of the page.
3. Click on `Add to Dock` in the dropdown menu.
4. Choose a name for the shortcut. We recommend you to write your Spot name or "MeltingSpot". Click `Add`.
5. Find MeltingSpot icon within your applications in your *Dock*.
6. Access your Spot by clicking on the new Favicon. It will open on a dependent navigation window (just *like* an application).

{% embed url="<https://www.loom.com/share/872de4092f2f45a4b513fca2cb94cdae?sid=a5e60ec0-462d-411c-b4a8-8448ee1f31b4>" %}
{% endtab %}

{% tab title="Android" %}

1. Open your Spot sur Chrome.
2. Click on the menu (3 dots icon) on the top-right corner.
3. Click on `Add to Home screen`.
4. You might be asked to choose a name for the shortcut. We recommend you to write your Spot name or "MeltingSpot". Click `Done`.
5. Close the window, and find MeltingSpot icon within your applications on your home screen.
6. Access your Spot by clicking on the new Favicon.&#x20;

{% embed url="<https://www.loom.com/share/d24162ea7f58446299443e70465b07e1?sid=70f84d26-b83b-4a74-8d8f-130d63ccfbd0>" %}
{% endtab %}

{% tab title="Windows" %}

1. Open your Spot sur Chrome.
2. Click on the `Install` icon next to the URL.
3. Find MeltingSpot icon within your applications on your *Desktop* and in your *Dock*.
4. Access your Spot by clicking on the new Favicon.&#x20;

<figure><img src="https://3055204660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrzBxnWaSListMwx3rzKu%2Fuploads%2F4Oo9DkLQgeoaNvLzMlx8%2Fimage.png?alt=media&amp;token=9723e393-decc-46db-b0c0-c557af3fc4a2" alt=""><figcaption></figcaption></figure>
{% 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.meltingspot.io/english/how-to/add-meltingspot-to-your-phone-computer-home-screen.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.