A web-based platform for remote debugging and management of Android devices, enabling real-time control from a browser.
STF (Smartphone Test Farm) is a web application that enables remote control, debugging, and management of Android devices from a browser. It centralizes device fleets for testing and development, allowing teams to interact with physical hardware without direct access.
Android developers, QA testers, and DevOps engineers working with multiple devices in lab environments, such as those in continuous integration pipelines or large-scale app testing.
STF provides a comprehensive, browser-based interface that mirrors physical device interaction, with features like real-time screen viewing, ADB integration, and device booking systems, making it scalable for team-based workflows.
Control and manage Android devices from your browser.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides real-time screen viewing up to 30-40 FPS via minicap, along with keyboard input, multitouch gestures, and drag-and-drop APK installation, enabling full device interaction from a browser.
Seamlessly integrates with ADB for shell command execution, log viewing, and reverse port forwarding, allowing debugging with IDEs like Android Studio and Chrome DevTools remotely.
Includes booking and partitioning systems for allocating devices to users or projects with scheduling, plus administrative controls for inventory monitoring and group management in multi-user environments.
Supports Android versions from 2.3.3 (SDK 10) to 15 (SDK 35), including Wear OS and custom distributions like Fire OS, without requiring root access.
Requires multiple system dependencies like RethinkDB, GraphicsMagick, ZeroMQ, and Node.js up to 20.x, with no Windows support and manual steps for setup, making deployment non-trivial.
Built for trusted internal networks, it lacks encryption between processes and does not fully reset device data between uses, posing risks in multi-user or public deployments as admitted in the README.
Prone to USB-related issues and device disconnections requiring manual intervention, with specific hardware recommendations needed for reliable operation, adding maintenance overhead.
Only supports Android devices currently, with iOS support listed as a long-term goal but not implemented, restricting its use to Android-centric workflows.