> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/connectivity/wordpress-connectivity/website-to-app-sync.md).

# Website-to-app sync

### Does AppMySite support plugins and website functionality?

#### **1. WordPress & WooCommerce**

AppMySite is designed to integrate seamlessly with the core functionality of **WordPress** and **WooCommerce** websites. However, plugin compatibility may vary based on their support for the official **WordPress REST APIs**:

* **Plugins Supporting REST APIs**:
  * Plugins integrated with the official WordPress REST APIs are more likely to function smoothly within your app.
  * These plugins can interact effectively with the app's infrastructure, ensuring seamless operation.
* **Plugins Without REST API Support**:
  * If a plugin does not support the REST APIs, your app may face limitations in functionality.
  * For example, custom functionalities or plugins that rely on non-standard APIs might require additional adjustments.
* **WooCommerce Optimization**:
  * The WooCommerce to App model is optimized to work with most plugins and content forms found on WooCommerce websites.
  * While core WooCommerce functionality is fully supported, certain third-party plugins may require testing to confirm compatibility.

{% hint style="success" %}
Use advanced web-view to support features that are not natively supported, while offering a completely professional app experience to your users. 
{% endhint %}

Follow this guide to use web-view for WordPress:

{% content-ref url="/pages/hsD4f343cpsg5oxjnRCO" %}
[Web-view for WordPress](/app/web-view/web-view-for-wordpress.md)
{% endcontent-ref %}

**2. Web to App**

With the **Web to App** solution, your app will support all functionalities present on your website by leveraging advanced web views. This means your app can render your website exactly as it appears on a browser, ensuring compatibility with most plugins and features.

* **Advanced Web-View Features**:
  * The web view technology provided by **Google** and **Apple** powers this solution, ensuring a professional and responsive app experience.
  * Your app will offer a complete native-like experience to users, regardless of the complexity of your website’s functionality.

Follow the guide to learn more about the advanced web-view settings:

{% content-ref url="/pages/sgZw0r2MP57mpnx7mrqD" %}
[Advanced web-view settings](/app/web-view/advanced-web-view-settings.md)
{% endcontent-ref %}

* **Considerations for Compatibility**:
  * While the Web to App solution supports your website’s full functionality, certain features may behave differently depending on how they interact with websites.
  * Testing is recommended to ensure all functionality meets your requirements.

{% hint style="warning" %}
It is important to note that the web view in the app is controlled by the technical infrastructure provided by Google and Apple. 
{% endhint %}


---

# 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://docs.appmysite.com/app/connectivity/wordpress-connectivity/website-to-app-sync.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.