> For the complete documentation index, see [llms.txt](https://faq.growsensor.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.growsensor.co/the-grow-app/how-do-i-use-the-grow-graphs/how-do-i-interact-with-graphs.md).

# How do I interact with graphs?

Unlike our competitors, the Grow App's graphs are fully interactive, making it easy to explore your data in real time.

* Scroll through the list of graphs to access individual sensor data.
* Pan across the timeline to focus on specific dates or times.
* Pinch to zoom in or out for a detailed or broader view of trends.
* Use shortcuts to instantly switch between hour, day, night, month, and year views for quick insights.
* Tap the graph to load a data pointer. This will show the exact reading at that moment, along with any limits you've set.

The Grow App makes reviewing your data fast and effortless. It has zero loading times, and you don't need to rotate your phone or navigate hidden menus. 

Every interaction is designed for smooth, instant access to the insights that matter most.

Here's a video of the graphs in action:

{% embed url="<https://www.youtube.com/watch?v=Il_bgeYCeLM>" %}

<br>


---

# 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://faq.growsensor.co/the-grow-app/how-do-i-use-the-grow-graphs/how-do-i-interact-with-graphs.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.