Help confirm how Beebo works on the equipment people actually use. Choose a few features, follow a practical checklist and tell us what happened. Clear reports of success are as useful as clear reports of a problem.
AI-assisted checks are a starting point. Human confirmation comes next. Built features with passing automated checks still need real people to confirm the experience on their devices. This does not certify every feature, platform or current release. Read the testing status record.
Use the community for discussion and general feedback. Joining the community or applying on this website does not enroll you in the official Android closed test; accepted participants receive separate opt-in instructions.
Your results help everyone.
Use a platform-specific checklist to record what works, what fails and what should change. Photos and short videos go to Nick’s private review. With your permission, reviewed anonymous checklist counts can appear on the public results page.
October 14, 2026: previous release and test recordStart here / About 20 minutes
Your first tester checklist.
Start with these eight checks, then pick one area below. Use the exact build in your invitation and permitted sample media. You do not need to test everything.
Testing can start before the visual redesign is finished. Test the stable interface in your installed build. When an updated design arrives, repeat the affected checks. Design previews and automated checks are not real-device passes.
Tick boxes to track this session only; they are not saved or submitted and may reset when you refresh. A tick means you completed the check, not that it passed. Record Pass, Fail, Blocked, Not run or Not applicable using the result template.
The full checklist covers remote routes, offline downloads, Campsite guests, each assigned game, permissions, photos, music, supported TV features, accessibility and updates. Paid-service tests use invited test access; testers do not need to make a purchase.
Use the community safely: post ordinary results in #test-results and reproducible bugs in #bug-reports. Send privacy/security concerns privately to Nick. Never post passwords, private media, recovery keys or unredacted logs.
Checklist updated Oct 14, 2026, 6:36 AM Eastern. Community reward conditions remain unchanged. No store rating or review is required.
Help build the Beebo community
One owner. A community of testers.
Nick is the sole owner of Beebo Entertainment and the only administrator in our Discord community. Everyone here is part of the tester community. Whether you are exploring Beebo for the first time or helping someone else, your honest feedback helps us improve.
Beebo is looking for volunteer community help as we prepare to launch. You do not need to be a developer: clear feedback, a patient answer and a useful guide can all make a difference.
Find a team where you can help.
We need customer support helpers (CSR), a testing team and community helpers. Welcome newcomers, answer setup questions, reproduce bugs, write guides and keep discussions friendly and useful.
Helpers are volunteers, not additional administrators. Nick remains the only administrator and handles account decisions, rewards and escalations. Tell us your time zone, usual availability and relevant experience; Nick will agree the responsibilities with you.
Beebo Community Guide Rewards.
If you help another community member solve a real Beebo question, you may request a review for a Community Guide reward. Both people must agree that the relevant messages may be reviewed. Send links to the relevant Discord messages, or a redacted copy, with the question, advice, outcome and the other person’s confirmation of whether it helped.
We may use automated tools to organize a submission, but Nick makes the final decision. Do not submit passwords, account emails, IP addresses, QR codes, private media details, access codes or unredacted logs. Rewards recognize accurate, useful assistance. They never depend on referrals, purchases, installs, ratings, reviews or positive feedback.
Honest feedback is what matters. Reporting a problem is welcome. Community rewards recognize useful contributions, not any store ratings, store reviews or promotional recommendations. You do not need to make a purchase.
We are building a group of people who can try the Android app regularly, remain enrolled for the full test and send useful feedback. This is a recruitment goal, not a statement that twelve people are enrolled or that the required days have already been completed.
For personal developer accounts created after November 13, 2023, the official rule requires at least 12 testers continuously opted in for the preceding 14 days before applying for production access. Beebo’s account type is unconfirmed. Meeting the threshold does not guarantee approval; meaningful engagement matters. Official Android closed-testing requirements.
Follow your official invitation and opt-in instructions. The fourteen-day period concerns continuous enrollment, not the day you applied here or downloaded an APK. We do not require payment, positive reviews or store ratings.
01 / Start with one useful result
You do not need to test everything.
Record the setup
Note Beebo version/build, where you installed it, device model, operating-system version and the date. For playback, include the source computer and player. For remote access, include the route shown by the app.
Use a small test library
Choose your own or authorized sample files. Use copies for file-transfer, removal and recovery tests. Keep your ordinary account and irreplaceable media separate from any invited destructive test.
Follow the invitation
Some platform builds, optional modules and managed services need an invitation or entitlement. If a build or control is not available, mark that step “not available” or “not run.” Do not mark it passed.
Report what happened
Try the same steps again when practical. Include both expected and actual behavior, how often it happened and whether a restart or network change affected it. Screenshots are optional.
Closed-test invitation and website download are separate routes.
Release labels follow the published feeds. Always report the version installed on your device; an earlier source check is not a result for a later installer.
02 / What human testing adds
Check the experience, not just the code.
Automated cases can check a setting, policy or request in a controlled setup. They cannot establish the picture on your TV, the sound from your receiver, the behavior of your phone’s hotspot or whether a screen reader makes a workflow understandable. Human sign-off belongs to a recorded feature, build, device and connection.
✓ Real testing confirmed✓ Built · local checks passed• Verification pending~ Work remains× Not offered
A pale-green check applies only to the listed passing checks. Dark green requires a matching real-test record. A feature may also be unavailable, disabled or awaiting activation; its evidence label does not remove those limits.
Read the scope and dates behind the automated checks
The published feature review describes desktop source 0.1.59 and Android source 1.42 (build 43). Its appearance record has 61 passing local checks at source revision 62eb6cb. Those are setting/definition checks, not a human review of every rendered screen.
A later selected run on September 23, 2026 used source revision a27e073d77e842f0710599ef98ee3d8d6c0a112d. The results below are historical results for that revision. They do not establish the status of a newer source or downloaded build.
Selected automated checks at revision a27e073
Scope
Passed
Failed
Skipped
Desktop appearance and preferences
193
0
0
Account and connectivity backend, using test fixtures
145
0
0
Local service adapter
42
1
16
The service suite included a configuration-inventory consistency failure and optional-driver skips at that revision. Its isolated Linux repetition recorded the same 42 passed, 1 failed and 16 skipped; these repeated cases are not additional unique features. Current revalidation is a separate step.
Newer runs, October 5, 2026, on the code from release night (a few hours before the final release commit, not on it): on a Linux test machine 739 of 739 Windows-app test files, 951 of 951 server tests and 506 of 508 service tests passed (2 skipped because they need Windows or a missing tool). These are automatic tests, not device results; see what’s new and what’s tested for the October 5 phone and casting checks.
These selected runs did not test a real phone, TV, live VPN tunnel, billing transaction or every media/network combination. Older saved Android reports overlap across distributions and do not prove behavior on a current device. See the published evidence record for the earlier review and its limits.
03 / Choose your area
The checks that help most.
Start with one of the priorities below. Open an area for a sequence to follow, then include the conditions and result in your report.
01 / FIRST PRIORITYAccounts, household permissions and privacyUse a test owner account and an invited adult test profile, with sample media and files.
Try this on your equipment
Create or join the household through the provided invitation. Sign in, sign out and sign in again on a second device. Record whether the correct household and profile return.
Give the second profile a small permitted library. Check search, posters, playback, downloads and shared links as that profile. Confirm that unshared files and another profile’s private information stay unavailable.
Change a permission, remove a test invitation and sign out a test session. Check the result on the second device after refresh and restart; record any delay.
Use password recovery or two-factor sign-in where available on your own test account. Verify success, an expired link and cancellation without sharing codes or recovery keys.
For deletion or subscription-lifecycle testing, use only a disposable test account and an assigned test plan. Record deletion and subscription cancellation separately; do not delete your everyday account.
Record: Report the two device/build combinations, role and selected permission, expected visibility and actual result. Send any unexpected private-data exposure directly to the tester address, without reposting the data.
02 / CORE EXPERIENCEWindows server and everyday playbackA Windows 10 or 11 computer, the published installer, and a few authorized sample files.
Try this on your equipment
Record the installer version, install type (new or update) and Windows version. Start Beebo, choose a small test folder and confirm that the library appears.
Play a short movie and an episode. Pause, seek near the end, resume after closing the app and switch to another signed-in profile. Check that progress belongs to the right viewer.
Try a subtitle and another audio track. Record the source codec, resolution and whether Beebo reports original playback, remux or conversion.
Compare local playback on the server with a second device on home Wi-Fi. Note buffering, sound, subtitle timing, CPU/GPU behavior if visible, and what happens when the player reconnects.
Restart the app and computer. Confirm folders, library progress and your selected layout are preserved.
Record: Include the device playing the file as well as the computer serving it. A successful 4K original file does not establish 4K live conversion. Windows setup · Playback paths
03 / PHONE & TABLETAndroid installation and daily useAn Android phone or tablet and an approved download or invitation for the distribution you are testing.
Try this on your equipment
Record app version/build, Android version and distribution: website download, closed store test or another supplied test build. Install using the corresponding instructions.
Connect to your own Beebo server. Browse, search, open a title, play, rotate the device and return from background. Check reconnecting after the screen was locked.
Try subtitles, track selection, continue-watching and profile switching. Compare the same title on home Wi-Fi and an approved away-from-home route.
Check permission prompts when first downloading, sharing media or using a microphone-related feature. Declining a permission should produce useful guidance rather than an unexplained failure.
Try the relevant download and camp checklists below. A feature omitted from your distribution is not a failed test: report it as unavailable and name the distribution.
04 / TAKE IT WITH YOUDownloads, offline playback and updatesAn installed phone app, free storage and a small set of authorized sample media.
Try this on your equipment
Download one movie and a few episodes. Record the selected size/quality, queue order and final file size where shown. Try pause, cancel and retry on sample downloads.
For an interrupted download, briefly disconnect the test device, reconnect and check the queue. Record whether partial content is clearly identified and recovery duplicates anything.
Finish a download, then turn off the source computer and disable internet on the playback device while keeping any local network needed for the test. Play, seek and resume the prepared file.
Remove a downloaded test copy using the app. Verify which copy was removed; your source library should remain as expected.
Update from your installed version using the published route. Confirm version/build changes, sign-in, settings, download inventory and resume position. If your build has no newer update, report that step as not run.
Record: Record available storage, selected download option, source/target versions and whether the source computer and internet were on or off. Do not infer offline readiness from a completed progress bar alone.
05 / CONNECTION ROUTESDirect and owner-operated access away from homeA running home server, a phone on a separate network and permission to manage your own connection.
Try this on your equipment
First confirm the same title plays at home. Turn off the phone’s home Wi-Fi and test over mobile data or another network you are allowed to use.
Read the route identified by Beebo during the session. Record direct, router/port mapping, your own relay or managed Relay; playback alone does not prove the route.
For your own compatible relay, use your own configuration and check the provider’s traffic view privately. Record only the route type in the report, never credentials or private addresses.
Play, seek, change quality and reconnect after a brief connection interruption. Keep the source computer awake and online.
Compare the route before and after reconnection. If a fallback is used, record the displayed route and entitlement without assuming every network uses the same policy.
Record: Entertainment and your compatible owner-operated route have no Beebo software/relay fee; outside provider costs are separate. Connection guide · Own relay guide
06 / OPTIONAL SERVICEBeebo Relay and household stream limitsAn invited or otherwise authorized Relay test account, a running home server and the assigned test entitlement.
Try this on your equipment
Use the connection settings supplied for your test. Verify the app identifies Beebo Relay while your session is actually using it.
Start a video, seek and change quality. Briefly interrupt the viewer’s connection, then reconnect and record playback recovery and the route label.
With permission from the household owner, start the number of concurrent streams included in the assigned test plan. Try one more on a test device and record the message and session behavior.
Stop a stream and retry the waiting device. Check that capacity becomes available and sessions do not remain counted indefinitely.
If asked to test activation, cancellation or billing recovery, follow the invitation’s test environment. Do not make an unrequested purchase or assume an informational price card activated a plan.
Record: Paid Relay plans are Planned and not available to buy yet. Relay status · See pricing
07 / SEPARATE SERVICEBeeboVPN connections and recoveryAn approved VPN test entitlement and a supported device identified in your invitation.
Try this on your equipment
Record the VPN client/build, device OS and selected location. Connect, verify the displayed state and confirm ordinary internet access.
Disconnect and reconnect. Compare the app’s state with actual access, including after sleep, app restart and a permitted network change.
If kill-switch or bypass settings are available in your assigned build, check them with harmless test traffic and the supplied instructions. Record settings and behavior, not a blanket security conclusion.
Check the assigned connection allowance using your own test devices. Record the message when a limit is reached and the result after disconnecting one device.
Report failures to reconnect, unexpected traffic behavior and entitlement messages with timestamps. Do not include public IP addresses, credentials or private destinations in a public screenshot.
Record: VPN is a separate optional service; it is not included in the Entertainment free-software statement. VPN status
08 / PEOPLE TOGETHERCamp Mode, QR joining and local gamesAn Android host with prepared files, at least one guest phone and a local hotspot or shared Wi-Fi.
Try this on your equipment
Prepare a small authorized download while online. Start Camp Mode and record host model/build, guest model/browser and whether internet is unavailable.
Follow both joining steps: connect the guest to the local network, then open the camp session. Check QR scanning, the fallback instructions and joining with a session nickname.
Start one game suited to your group. Record its exact title, number of players, selected play mode and whether guests can take turns and see the same state.
Lock a guest phone, return to the browser and reconnect. Check a late join, a player leaving and a new round. Record any lost turns or scores.
Play a prepared local video with the source computer off. Check sound, seeking and returning to the camp menu. Test shared photos or another activity only where your build offers it.
Record: The catalogue contains 46 games/activities: 42 campsite entries and four independent solo games. Test each game separately; the website catalogue is not a playable demo. Choose a game · Camp setup
09 / LOCAL NETWORKHome viewing without internetA working local library and local Wi-Fi; arrange a short test when disconnecting internet will not disrupt anyone.
Try this on your equipment
While online, open the intended library and record the local server address privately. Confirm the sample movie and music track play.
Disconnect only the internet/WAN route while keeping the local router and Wi-Fi running, or use an equivalent isolated test network.
Open the server’s local address and play the sample files. Check cached posters, search and useful offline messages.
Restart the player and try a title whose details were not previously cached. Record what still works and what needs internet.
Restore internet and check recovery. Remote Relay, VPN and fresh online metadata are separate from local playback and require internet.
Record: State exactly what was disconnected and what stayed connected. A local-only session and a fully offline prepared phone download are different tests.
10 / EVERYDAY COMFORTLayouts, settings and personal preferencesA current desktop build and a few minutes with your normal library.
Try this on your equipment
Write down your chosen layout, theme, sidebar behavior and poster density. Change one setting, restart and check it persists.
Try at least one compact and one larger window size. Check long titles, empty libraries, search results and opened dialogs.
Switch between the layouts available in your build. Check that navigation, focus and access to settings remain usable.
If invited to test a layout import, export or back up your preferences first. Compare personal sidebar overrides before and after; report unexpected resets.
Keep the report tied to the packaged app you used. Standalone website theme previews are not proof that a native desktop theme has been installed.
Record: Record the exact layout/theme names, build and display scaling. Appearance guide
11 / ACCESS FOR EVERYONEKeyboard, screen readers, text and translationsYour usual keyboard, accessibility tools or native-level knowledge of a supported language.
Try this on your equipment
Navigate sign-in, library, title details and settings using only the keyboard. Record missing focus, unreachable controls or a place you cannot leave.
Open and close dialogs. Confirm focus moves into the dialog and returns to a sensible control afterward.
With your screen reader, listen for names of buttons and fields, selected states and result announcements. Include the reader and version in the report.
Try 200% text scaling, high contrast and reduced motion. Look for clipped controls, unreadable status labels and unwanted movement.
For translations, name the language and screen, then quote the unclear text and suggest a correction. Record dates, plurals and mixed-language interface text separately from media titles.
Record: Supported language coverage includes English, Spanish, French, German, Brazilian Portuguese and Italian; this is not a claim that every screen or translation has passed human review. The translations were made with a machine’s help and no native speaker has read them yet.
ADDITIONAL PLATFORMLinux desktop serverA supplied Linux build, a compatible desktop system and authorized sample files.
Try this on your equipment
Confirm the available artifact and its instructions on the platform page or in your invitation before installing.
Record distribution/version, architecture, package type and desktop environment. Install, start, choose a small media folder and run the core playback checklist.
Check file permissions, a path containing spaces, restart behavior and local-network access from a second device.
Record hardware-conversion availability and fallback behavior only for your actual GPU/driver combination.
Record: Do not equate source presence with a released installer. Linux availability
ADDITIONAL PLATFORMDocker and NAS hostingYour own compatible test server/NAS, an available image and storage containing test copies.
Try this on your equipment
The Docker image is not offered for download right now; only test it if your invitation supplies an image. Use the supplied image/tag and setup guide. Record architecture, host OS and container runtime; keep credentials out of screenshots.
Mount a sample library and configuration volume. Check the configured read/write permissions and whether folders are visible.
Play locally from another device, restart the container and confirm library/settings persist.
Check an authorized update and hardware acceleration only if those steps are part of your invitation. Report image version and permission-related messages.
ADDITIONAL PLATFORMAndroid TV, Google TV and Fire TVA compatible device and the exact TV build or browser route approved for testing.
Try this on your equipment
Confirm an installable artifact or supported browser route before starting. Android TV uses the website Android app; Fire TV has an in-development tester build with a Fire TV install guide. Record device model, OS, app version and installation route.
Use only the remote to sign in, browse, search, open a title, pause, seek and return to the library.
Check the Back button, visible focus, on-screen keyboard and recovery after sleep.
Report subtitles, audio track and playback route for each sample, including any remote control that has no effect.
ADDITIONAL PLATFORMRoku devices and TVsA device and a test invitation with an available channel/build or explicitly supported route.
Try this on your equipment
Use the in-development tester channel and the Roku install guide (installed from a computer on the same Wi-Fi); there is no public channel in the Roku store.
Record model, system version and channel/build. Test sign-in, remote focus, browsing and a short authorized video.
Check pause, seeking, subtitles, Back and resume after sleep using the supplied feature scope.
ADDITIONAL PLATFORMSamsung and LG smart TVsYour own TV and an available test build or supported browser route.
Try this on your equipment
Record TV model/year, system version and whether you used an app or the TV browser. LG: an in-development tester app with the LG install guide (Developer Mode). Samsung: no install file yet; use the TV’s web browser.
Test sign-in and every main action with the TV remote. Note unreadable text, keyboard limitations and lost focus.
Play an authorized sample, seek, change an offered subtitle/audio option and return after standby.
Record: Report the exact TV and route; one brand/model result does not confirm another. Smart TV status
INVITED INTEGRATIONCompatible clients and owner integrationsAn explicitly supported client or integration and accounts you control.
Try this on your equipment
Record client and server versions and the supported connection method. Use only your own test account and sample library.
Check sign-in, library visibility, playback and sign-out for that integration; keep private URLs/tokens out of reports.
If testing an owner webhook or API, use the provided test instructions and a destination you control. Record expected and actual events without posting payloads containing personal information.
Record: Compatibility is specific to the client, version and feature. Integration scope
PERSONAL LIBRARYMusic, photos and Space SaverYour own sample music, photos and disposable file copies; a phone and your home server.
Try this on your equipment
Play a music queue, change tracks and return after locking the phone. Record background and resume behavior for your distribution.
Open a photo album and a permitted shared view. Confirm who can see each album and whether unshared media stays private.
For Space Saver, copy a small disposable test folder home. Open the destination files and verify the originals remain until you explicitly choose a removal action.
Test interrupted transfer recovery with those copies. Report duplicates, missing files and storage messages; keep your irreplaceable originals backed up.
Email testers@beeboentertainment.com with the test area in the subject. Copy this template and fill in what you can. Use “passed,” “failed,” “blocked,” “not run” or “not available” for each step.
Test area and feature:
Date and time zone:
Result: passed / failed / blocked / not run / not available
Beebo version/build and distribution:
Source/server version, if different:
Device model and operating-system version:
Other device, browser or receiver involved:
Connection route shown by Beebo:
Sample media format, resolution and selected quality:
Steps I followed:
What I expected:
What actually happened:
Can I repeat it? (for example, 2 of 3 attempts)
What changed after restart or reconnection:
Screenshot or short recording: optional, with private details removed
A useful success
“Windows 0.1.79 served my authorized 1080p sample to Android 1.51-tester11 (build 61) on home Wi-Fi. Original playback, subtitles and seeking worked for 25 minutes. After closing and reopening, it resumed within a few seconds of my saved position.”
Example report format only; this is not a published test result.
A useful problem report
“In Camp Mode, guest two lost the turn indicator after locking the phone. I rejoined using the same local session. It happened twice in three attempts. The host and first guest continued normally.” Add the game, builds and device details.
Example report format only; this is not a known-issue statement.
Send unexpected private-data exposure, unintended file removal or an unexpected charge privately and promptly. Stop repeating that operation with personal data; describe what happened using sample names. Remove passwords, access tokens, invitation codes, email addresses and private media/location details from attachments.
A report is reviewed before a public status changes. “Works on this device under these conditions” is a useful conclusion; it does not approve every other platform.
Up to 60 approved testers, with a separate waiting queue of up to 60 applications. These counts cover this website’s new application system, not older email requests or official store enrollment.
—Applications received
— / 60Approved testers
— / 60Awaiting review
Loading live availability…
See what people plan to test — no names
A person may choose several areas. These are testing intentions, not completed checks. Private notes, creator tags and referral groups are not published.
Anonymous testing plans by platform and area
Main platform
Testing area
Waiting
Approved
No testing plans have been recorded in the new system yet.
Nick reviews every application. Only email, username, password and your testing choices are required. Other information is optional. Applications go to his private dashboard, with no email sent for each signup.
Your application account lets you check your place in the queue. It is separate from a Beebo media account and does not grant access to anyone’s library, a paid service or a store test track.
Check your application.
What happens after you apply?
Choose your main platform and testing areas.
Nick reviews applications in his dashboard and accepts up to 60 testers.
Check your application status here. Any store invitation or specific test assignment is arranged separately; no automatic approval email is promised.
Use the platform checklist to report what worked, failed or could be improved.
Your application stores your email, application username, salted password hash, testing choices, optional details and submitted referral code. Nick can review contact details, creator claims and referral groups; passwords are never shown. Your contact email has not been automatically verified. Your feedback includes the details you choose to send. They are used to coordinate testing. A store invitation may require sharing the relevant account address with that distribution service; follow your invitation.
Results may be summarized without naming you. Do not send your media collection, passwords, recovery keys, payment-card details or unredacted private logs.
Email the tester address to ask for deletion of your submitted details or to leave.
Pre-release software may fail or lose settings. Back up important data and use test copies where a checklist changes files. Testing does not guarantee a product release, store approval or a place in the programme.
Community help and rewards updated Oct 14, 2026, 10:48 AM Eastern. Testing guide reviewed Sep 23, 2026, 11:54 PM Eastern.
Help shape what comes next.
Nick welcomes practical suggestions that improve Beebo without adding unnecessary clutter. If your idea becomes part of the app or platform, he may offer service credit or another thank-you, agreed individually. Suggestions and honest criticism are welcome; no positive rating or store review is required.
The long-term goal is a lightweight movies-and-TV core with optional extras, plus easier poster setup once suitable commercial licensing can be funded. Read Nick’s community roadmap →