Dark green needs an identified feature, build and device or network test. One passing phone does not validate every platform.
BeeboENTERTAINMENTHow Beebo comparesEVIDENCE, NOT ASSUMPTIONS
Built. Checked. Clearly explained.
Beebo has a broad implemented feature set. We show local checks and real-device testing separately so you can see what is known before installing.
Review date: . Source snapshot: desktop 0.1.59 and Android 1.42 (build 43). Source versions do not prove that every download contains every later change.
What each symbol means
Pale green means the listed local checks passed. A person still needs to check the feature on the stated device. “Tester needed” uses pale green too.
Yellow means the implementation is incomplete or an identified part is still being built.
Red means that particular capability is not offered. A similar feature may exist, but it must be described separately.
Verification pending means evidence is not yet sufficient for a pass label. It does not mean a test failed. Download availability, settings and billing activation are separate from testing.
What this review checked
| Area | Evidence | What remains |
|---|---|---|
| Desktop appearance settings | ✓ 61 local checks passed Four appearance-related test files were run on September 23: 61 passed, 0 failed, 0 skipped. They cover theme/preset validation and saved preference schemas, including nine layout packs. | Visual and interaction testing of every layout, screen size, keyboard flow and actual packaged app. This is not a claim that all UI features have passed device testing. |
| Playback pipeline | Earlier local integration records include original-file range requests, negotiation, remuxing, subtitles and selected browser playback on desktop 0.1.58. Technical guides identify that historical scope. | A new candidate’s GPU, codec, HDR, audio receiver, network route and device combinations. Live output profiles currently stop at 1080p; 4K original playback is a separate path. |
| Android local test reports | Saved reports inspected on September 23 record 2,521 web-build tests, 2,521 store-build tests and 2,518 alternate-store tests with no recorded failures. Many overlap across distributions. | These suites were not rerun by this website review or tied to a new release artifact. They are not a unique total of tested features or proof of real-phone behavior. |
| Games catalogue | 46 entries checked against the app catalogue: 42 main catalogue games and activities plus 4 independent solo puzzles. Each game’s mode matters; some require guests. | Game-by-game device checks, current screenshots and separate public browser demos. The website catalogue itself is an information guide. |
| Camp QR, guest play and prepared downloads | The owner reported successful use of these flows. Supported offline guests connect locally to the host phone. | A release-bound test record with exact host/guest devices, browser, hotspot and offline conditions. Distance, hotspot limits and battery affect a session. |
| Relay and VPN | The owner reported working connections. Code and service configuration need separate validation from a single successful session. | Account lifecycle, final billing activation, per-plan enforcement and tests across supported networks and locations. |
Availability is a separate question
The download cards show the published Windows and Android versions and timestamps. Other platform pages describe their own artifacts and tester routes. A source implementation or automated build does not imply store approval or a ready-to-install download for every platform.
The optional AV1 conversion path is off by default and requires a compatible player and available encoder. Stories, casting, billing and other features vary by Android distribution. See the technical guide and the per-platform comparison.
Help turn a local check into a device result
- Record your Beebo version, device model, operating-system version and app distribution.
- Choose one feature and note its settings, source format and connection route. Use your own or authorized demo files.
- Write what you expected, what actually happened, and whether you can repeat it.
- Include failures as well as successes. Remove passwords, email addresses, access codes, personal media names and location information from screenshots or logs before sharing.
- Submit your result through the tester page. A result is reviewed before a public status changes.
Explore the detail
Complete feature guide · 46 games and how to play · Technology and versions · Free and planned paid options