Build & Test Overview
Building and testing your Median app is the path from configuration to deployment. This section covers how to use Median App Studio, development tools, and platform-specific build and deployment workflows so you can run your app on simulators and devices and publish to the App Store and Google Play.
Related Documentation
Median App Studio
Use the cloud-based App Studio to configure your app, preview changes in browser simulators, and manage builds without installing Xcode or Android Studio.
App Download
Install your app on iOS and Android devices for testing. Get IPA (iOS) and APK (Android) builds and install them on physical devices or use TestFlight for iOS distribution.
Development Tools
Debug and optimize your web experience with browser dev tools, inspect network and console, and use Median's developer resources for testing app behavior.
iOS Build & Deployment
Build iOS binaries (IPA), configure signing, connect to App Store Connect, register test devices, upload to TestFlight, and publish to the App Store.
Android Build & Deployment
Build Android APKs and AABs, install on devices, connect Android Studio simulators to localhost, and upload to Google Play.
App Configuration & Management
Manage app identifiers, app configuration (appconfig.json), Google Services, backup, multiple app instances, and CI/CD integration.
What to Test
Median apps are composed of web content, native UI elements, and native functionality (such as haptics or biometrics) or SDK integrations from plugins. Test across these areas before release:
UI & UX
Validate the app interface and user experience across device types, orientations, and OS versions. Typical test cases include navigation, link handling, deep linking, accessibility, and offline behavior.
App Performance
App performance is strongly correlated to your web experience. Optimize site speed and remediate bottlenecks in JavaScript, images, and embedded functionality. You can also gain performance by using Native Navigation instead of web-delivered menus, and by leveraging native SDKs from third-party vendors.
Performance analysis tools:
For strategies on improving webview app speed, see the Median blog on speed and performance.
Native Device Features
Features like Haptics, Biometrics, or In-App Purchases require testing on physical devices and cannot be fully simulated in a browser or virtual device.
Plugin Configuration
Validate plugin configuration using median.dev demos or diagnostic tools. Median offers Solution Architecture and Engineering services to advise on plugin implementation. Diagnostic tools can help access log files for troubleshooting with our team or third-party vendors.
Testing & Development Tools
App Studio Simulators
Cloud-based virtual devices in Median App Studio let you quickly test configuration changes in a browser. You can switch between devices, operating systems, and orientations.
Simulator limitations — Some native device functionality and third-party SDKs integrated through plugins cannot be tested in simulators. We highlight those cases in the documentation with a warning label.
Browser Development Tools
Use your browser's dev tools to inspect, debug, and optimize your web experience: viewport, user agent, console, and network requests. See Development Tools for details and links to Chrome DevTools, Safari Web Development Tools, and Microsoft Edge DevTools.
Developer Demos
median.dev provides demos for JavaScript Bridge functionality and many app features. During development, you can replace the Website URL with a demo page URL on the Overview tab and create a new build. In production, add a link to the demo on your live site—for example, hide it behind a sequence of taps (e.g. searching for specific attributes) so real users don't see it.
Developer DemoDisplay our demo page in your app to test during development https://median.dev/share-function
If a demo works in your app but your own site does not: debug your page in the app using Development Tools, inspect the demo source in your desktop browser, and recheck your JavaScript against the documentation.
Physical Device Testing
Physical devices are the gold standard for testing native functionality and end-to-end flows. Distribute to devices via Upload iOS to TestFlight or Install Android APK.
When performing QA, you may need to uninstall older test versions:
adb and sysdiagnose
For in-depth logs, system information, and application metrics, use platform diagnostic tools: Android Debug Bridge (adb) and Sysdiagnose. See Development Tools for more on debugging in the app.
Mapping Test Cases and Tools
| Tool | UI / UX | App Performance | Native Device Features | Plugin Configuration |
|---|---|---|---|---|
| App Studio Simulators | Recommended — switch devices, OS, orientations | Not recommended — no detailed logs | Limited — simulators lack full native support | Limited — high-level info only |
| Browser Development Tools | Limited — user agent and viewport | Recommended — analyze web assets | Not recommended — native features not testable | Limited — console only |
| Appetize Debug Mode | Recommended — switch devices, OS, orientations | Limited — network logs available | Limited — simulators lack full native support | Recommended — device logs for plugin validation |
| Physical Device | Limited — device suite maintenance | Limited — device suite maintenance | Recommended — required for native features | Recommended — fastest way to validate plugins |
| adb and sysdiagnose | Not recommended — not ideal for UI/UX | Recommended — metrics and performance analysis | Recommended — logs and error codes | Recommended — best for SDK diagnosis and vendor engagement |
Summary
Use Median App Studio to configure and preview your app, Development Tools and median.dev to debug and test behavior, and iOS Build & Deployment and Android Build & Deployment to produce installable builds and publish to the stores. App Configuration & Management covers identifiers, config, and CI/CD so your build pipeline stays consistent.
Updated about 1 month ago