> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/app-builder/test.md). # mobile render test Building an enterprise-grade financial app is only half the battle. **Test** is your operational safety net — a sandbox to test, tweak, and verify your financial logic before going live. The **Mobile & Local Sandbox** mimics your live production environment. It bypasses app store approval pipelines, putting your compiled React Native code straight onto a physical handset for real-world testing. ## Why a real device * **Interactive Sandboxing:** Test custom components — a loan calculator, a transaction dashboard — under realistic conditions. Enter real numbers, tap buttons, and confirm the logic behaves as intended before pushing changes live. * **Touch-Optimized Edge Case Hunting:** Standard browser emulators miss real touch gestures. A live handset shows whether floating buttons, swipe elements, and input fields stay thumb-friendly across screen sizes. * **Instant Iterative Tuning:** Spot a UI glitch or logic flaw on the device, jump back into the builder prompt, send a follow-up instruction, and watch the rebuild refresh on your screen. * **Stakeholder Sandboxing:** Preview environments are isolated from internal active system files, so clients and compliance officers can review logic safely without exposing backend data. ## The mobile handshake Connecting your browser-based workspace to a physical device: 1. **Platform Selection:** Ensure your project target is toggled to **Mobile (beta)** in the header before generating — see [Build](/app-builder/build.md#building-for-mobile). 2. **QR Generation:** Once generation completes, the platform exposes a secure, project-specific QR code in the workspace preview dashboard. 3. **Expo Go Connection:** Scan the QR code with your phone's camera via the free, third-party **Expo Go** app. This mounts and renders your full application bundle on the phone in seconds. {% columns %} {% column %}

Bridging the gap between design and physical testing via Expo Go for real-device validation.

{% endcolumn %} {% column %}

Final high-fidelity prototype featuring thumb-optimized navigation and touch-friendly interface components.

{% endcolumn %} {% endcolumns %} You can also use the mobile previewer inside the builder to validate logic and branding on a simulated handset without leaving the workspace. Use the simulator to iterate quickly; use a real device before you publish. {% hint style="info" %} **Fix with AI** sends the reported issue to Qore's build agent. Review the rebuilt preview before you continue. {% endhint %} *** When the app holds up on a real device, move to [Deploy](/app-builder/deploy.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 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.uptiq.ai/app-builder/test.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.