> For the complete documentation index, see [llms.txt](https://alexander-ameye.gitbook.io/stylized-water/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alexander-ameye.gitbook.io/stylized-water/support/mobile-demo.md). # Mobile Demo In order to showcase performance and compatibility on mobile platforms, there is a mobile demo you can try out. **Note:** this demo was made with Stylized Water For URP version 1.0.0 and will be updated in the future to reflect the features and capabilities of version 1.1.0 I have tested my shader on my own Google Pixel 3A with the following specs. * Snapdragon 670 CPU * Adreno 615 GPU * 440dpi, 2220x1080 screen I get an fps of around The shader might not run as well on older devices, so try this demo first! ![](/files/-M1fHbymQObqVFpq-yoC) On the right side of your phone you'll see a toolbar. From top to bottom the following settings can be toggled. ### **Legend** * Water visibility (visible/invisible) * Camera mode (orthographic/perspective) * Advanced lighting (on/off) * Target fps (60fps/30fps) * VSync count (0, 1, 2, 3 or 4, set this to 0 for highest fps) * Performance stats (visible/invisible) You can download the mobile demo (.apk) here. --- # 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://alexander-ameye.gitbook.io/stylized-water/support/mobile-demo.md?ask=&goal= ``` `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.