Start here
Web beta test checklist
Before sending general feedback, try the core path once: profile setup, one Meli coach conversation, one Dear Me journal entry, one Stories post or reply, one support/report action, and one Connections follow.
BadgerSupport
Get help with Badger during beta.
Use this page for account issues, community reports, safety concerns, and beta feedback while the first web version is being tested.
Account help
Account or signup issues
If signup says an account already exists, try logging in with that email first. If email confirmation was turned off during beta, the account may already be active.
Safety
Safety concerns
Badger is not an emergency service. If someone might be in immediate danger, contact local emergency services or a trusted adult right away.
Report builder
Build one complete beta report.
Fill this in when a teammate hits a blocker, confusing path, visual mismatch, or safety concern. It keeps reports consistent enough to reproduce quickly.
Auto-captured context
Report host: Checking report host.
Report viewport: Checking report viewport.
Report time: Checking report time.
These fields help separate production, device, and responsive issues before a teammate has to answer follow-up questions.
Copy-ready report
Ready to copy.
Beta triage guide
Turn teammate feedback into launch decisions.
Use this after a teammate sends a report. It keeps the team focused on August 3 beta candidate readiness instead of mixing blockers, polish, and future product ideas.
Fix today
Blockers in signup, login, profile setup, Meli, Dear Me, Stories posting, reporting, or production loading.
Fix before candidate
Confusing recovery paths, broken copy, missing safety context, or major design mismatches on launch-critical pages.
Defer after beta
Nice-to-have polish, private direct messages, mobile-only refinements, and new features outside the web test route.
Same-day response rules
Reply with severity, owner, and the next check before asking for more opinions.
Keep one issue per report so fixes can be verified against one URL.
If production is slow or blank, check /status before editing code.
After a fix ships, rerun the same tester path and update the report with the production result.
Beta feedback template
Sort issues by severity.
Use severity labels consistently: blocker means you could not finish the task, confusing means you recovered but felt unsure, and visual means the page worked but looked wrong.
Blocker
You cannot finish the task or reach the next screen.
Confusing
You recovered, but the page made you unsure what to do.
Visual
The flow works, but the page looks wrong or off-brand.
Safety
Something feels harmful, targeted, private, or report-worthy.
Before sending
Keep reports reproducible and safe.
If login still fails, send the Badger team the email used, the approximate time, and the screen where the issue happened.
Use the report button on a post or reply when content feels unsafe, targeted, or harmful. Reports are private to moderators. Other users should not see who reported something.
Do not include passwords, private Dear Me journal text, full Meli conversations, or screenshots that expose another person's private information.
If something breaks, note whether it blocked the task completely, felt confusing but recoverable, or was only a visual mismatch.
Useful links
Create an account at /signup, log in at /login, read the safety overview at /safety, and review the privacy overview at /privacy.