> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/bravo-tags/components.md).

# Components

- [Autoplay Video](https://docs.bravostudio.app/bravo-tags/components/component-autoplay-video.md): Autoplays an audio-less video when the user is on that app page.
- [GIF](https://docs.bravostudio.app/bravo-tags/components/component-gif.md): A GIF will replace the content of the rectangle.
- [SVG Component](https://docs.bravostudio.app/bravo-tags/components/svg-component.md)
- [Web view](https://docs.bravostudio.app/bravo-tags/components/component-webview.md): A web page will replace the content of the rectangle.
- [Web Components using AI](https://docs.bravostudio.app/bravo-tags/components/web-component-using-ai.md)
- [Web view communication](https://docs.bravostudio.app/bravo-tags/components/web-view-communication.md)
- [LottieFile](https://docs.bravostudio.app/bravo-tags/components/component-lottie.md): A Lottie will replace the content of the rectangle.
- [Lottie-animated component](https://docs.bravostudio.app/bravo-tags/components/lottie-animated-component.md): Create stateful components with Lottie animations
- [Flexible text (Flexo)](https://docs.bravostudio.app/bravo-tags/components/component-flexible-text.md): The text box will expand down to fit the content connected via API.
- [Zoomable image](https://docs.bravostudio.app/bravo-tags/components/zoomable-image.md): Makes an image zoomable with pinch gesture.
- [Component states](https://docs.bravostudio.app/bravo-tags/components/component-states.md): Add states such as pressed and active to your UI elements.
- [Stateful component (like button)](https://docs.bravostudio.app/bravo-tags/components/stateful-component-like-button.md): Create components with default and active states
- [Setting up the backend of Stateful component (like button)](https://docs.bravostudio.app/bravo-tags/components/setting-up-the-backend-of-stateful-component-like-button.md): Managing the stateful components requires the creation of a database that keeps track of the state for each component, and API requests to exchange the information.
- [Haptic Feedback (Buzzz)](https://docs.bravostudio.app/bravo-tags/components/haptic-feedback.md): Make your phone vibrate when adding interaction on your apps, such as navigation links or any action.
- [Progress bar](https://docs.bravostudio.app/bravo-tags/components/progress-bar.md)
- [Rich text](https://docs.bravostudio.app/bravo-tags/components/rich-text.md): Display the same text style as the content you get from an API
- [Date, Time and Currency Formatter](https://docs.bravostudio.app/bravo-tags/components/date-time-and-currency-formatter.md)
- [Scrollable text](https://docs.bravostudio.app/bravo-tags/components/scrollable-text.md)
- [Text Lines & Truncation](https://docs.bravostudio.app/bravo-tags/components/text-lines-and-truncation.md)
- [Status bar](https://docs.bravostudio.app/bravo-tags/components/status-bar.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.bravostudio.app/bravo-tags/components.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.