Trust page
Testing Methodology
Nine test categories, applied on named hardware, reported with the device, the version and the date. Where no result has been produced, the scorecard says so instead of carrying a number.
The nine test categories
| Category | What it covers | Status |
|---|---|---|
| Installation | Install path, error handling, permission prompts on each device type | Not yet tested |
| Compatibility | Behaviour across phone, tablet, TV and emulator form factors | Not yet tested |
| Performance | Startup time, channel switch time, playback stability | Not yet tested |
| UI and navigation | Layout, D-pad reachability, accessibility of controls | Not yet tested |
| Stability | Crash frequency across a sustained multi-hour session | Not yet tested |
| Permission review | Manifest audit against the app's stated function | Not yet tested |
| Update behaviour | Update mechanism, signature continuity after an update, data retention | Not yet tested |
| Stream handling | Bitrate switching, buffering behaviour and recovery on a constrained connection | Not yet tested |
| Device support | Which named hardware models install and run the build | Not yet tested |
How results are reported
- The device model, Android version and app version string used.
- The date the test was run.
- The observed result stated plainly, including failures and partial results.
- Any condition that would make the result non-reproducible for another reader.
What is out of scope
We do not test, measure or rate the legality, licensing or content quality of any stream. We also do not publish speed or quality comparisons against paid services, because a comparison of a licensed service and a sideloaded app is not a like-for-like measurement.