> 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/frequently-asked-questions/general/native-vs-webview-app.md). # Native vs Webview app ### What is the difference between native and web view apps? When creating a mobile app, you can choose between different approaches depending on your goals, resources, and customer needs. Two common approaches are native apps and web view apps. Both have their own advantages and can help businesses deliver mobile experiences effectively. #### Native apps Native apps are built specifically for mobile platforms like iOS and Android. They are installed directly from app stores and make full use of device features. * Offer smooth performance and fast loading speeds * Support advanced mobile features such as push notifications, offline access, and device hardware integration (camera, GPS, etc.) * Provide a highly customized user experience tailored to the platform * Work best for businesses that want to deliver rich, feature-heavy mobile experiences #### Web view apps Web view apps display the content of your website within a mobile app shell. They are easy to set up and allow businesses to quickly provide a mobile presence. * Bring your website into an app format with minimal effort * Automatically sync content from your website, so updates are reflected instantly * Support essential app features like app store publishing and navigation customization * Work best for businesses that want a fast, cost-effective way to offer a mobile app without maintaining separate platforms #### Choosing the right approach * If your focus is on performance and advanced features, a native app is a great choice. * If you want a quick, efficient solution that mirrors your website in app form, a web view app can be ideal. {% hint style="success" %} AppMySite helps create both native and web view apps. Web view apps include native capabilities that access device features. You can control in-app visibility of your website content with advanced webview controls. {% 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appmysite.com/frequently-asked-questions/general/native-vs-webview-app.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.