Jumbly legal
Closed Beta Tester Guide
A practical guide for closed beta testers: what to play, what to check, how to report bugs, and what data is saved locally.
Last updated: July 7, 2026
These pages describe the current Jumbly closed beta and planned platform features in plain language. We will keep them updated as accounts, analytics, subscriptions, and wider launch systems mature.
Start Here
- Open /games first. That is the main closed beta play shelf.
- Play one or two featured daily puzzles before exploring the wider catalog.
- You do not need an account to test daily gameplay, sharing, streaks, or local progress.
- Use the same browser for repeat sessions if you want local streaks and stats to persist.
Tester Checklist
- Load /, /games, /profile, /archives, /friends, /leaderboards, /support, /privacy, and /feedback.
- Play at least one featured game from start to completion or reveal.
- Confirm the post-game result card appears and the puzzle locks after completion.
- Copy or share one spoiler-free result.
- Refresh after completion and confirm the saved result still appears.
- Check that archives show previous puzzle entries as view-only.
- Try one game on mobile and one on desktop if possible.
How To Report A Bug
- Use /feedback for most beta reports.
- Include the page or game, device, browser, what happened, what you expected, and whether you were signed in.
- For gameplay bugs, include the puzzle date or number and whether the issue happened before or after completion.
- For visual bugs, include your screen size or device model where possible.
- Avoid sending sensitive personal information in screenshots.
Browser And Device Checklist
- iPhone Safari: scrolling, bottom navigation, modals, sharing, and installed PWA behavior.
- Android Chrome: touch targets, keyboard behavior, scrolling, and native share sheet.
- Desktop Chrome: gameplay, modal close behavior, keyboard navigation, and copy result.
- Desktop Safari: layout, scroll behavior, local progress, and route loading.
- Tablet/iPad: card grid spacing, game board fit, and modal sizing.
Feedback Priorities
- Puzzle fairness: confusing clues, unclear feedback, overly easy puzzles, or solve paths that feel like guessing.
- Mobile comfort: cramped boards, tiny tap targets, keyboard overlap, or awkward scrolling.
- Trust: unclear privacy copy, confusing account prompts, unexpected login requests, or anything that feels too salesy.
- Emotional pacing: completion moments, mascot tone, streak motivation, and whether the experience feels calm.
Privacy Note For Beta Testers
Jumbly is local-first in closed beta. Many preferences, progress records, streaks, and test feedback may be saved on this device. Optional account and sync features may be tested later, but daily gameplay should not require login. Use Privacy Controls to review or clear device-saved Jumbly data.