> 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/good-to-know/faq/other-features.md).
# Other Features
### **Does Bravo support smart animate or additional gestures from Figma prototyping?**
Unfortunately, the Figma API doesn't provide all the prototyping properties, when they do we will be able to add it to Bravo. Having said that, you can implement some of these features using [Bravo Tags](https://www.notion.so/Bravo-Tags-Master-List-145bec845f0b4afaa9e3bb8321b218a8) (ex: slide menu). If you have a specific animation or gesture in mind, send us a [feature request](https://community.bravostudio.app/c/feature-requests/).
### **Can I add Google Admob or monetization feature to my app?**
Currently, Bravo doesn't support Google Admob or in-app paid features. You can add a [web view Bravo Tag](/bravo-tags/components/component-webview.md) or an image + open URL Bravo Tag to create your own "ad space" in your app, as a manual process rather than through Google.
### **Can I add e-commerce to my app?**
You can create e-commerce apps to sell physical products using our [payment with Stripe](/integrations/payment-with-stripe.md) feature. In-app payments to sell digital products and subscriptions is currently not supported.
### **Can I charge for my app in the app stores?**
Yes, you can set a price for the apps created with Bravo both when you publish it in the App Store and Google Play.
**Didn't answer your question? 🧐**
Let us know in the [Bravo Community](https://spectrum.chat/bravo-studio?tab=posts) so we can further help you!
---
# 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/good-to-know/faq/other-features.md?ask=&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.