Submitting Feedback
A floating feedback button is available on most pages of the app, making it easy to report bugs, suggest features, or flag problems without leaving your current workflow. It is hidden on the Live page, which is an immersive, full-bleed video surface — reach feedback from the header or Settings instead while there.
The Feedback Button
Section titled “The Feedback Button”Look for the circular button in the bottom-right corner of the screen. Clicking it captures a screenshot of the current page and opens the feedback form.
You must be signed in to submit feedback. If you are not signed in, the form will prompt you to sign in first.
On Mobile
Section titled “On Mobile”On small screens the button is docked just above the bottom navigation bar (accounting for the device’s safe area, e.g. the home-indicator area on notched phones). To keep it out of the way while browsing, it hides while you scroll down and reappears as soon as you scroll up or pause scrolling.
Feedback Types
Section titled “Feedback Types”Choose one of four categories when submitting:
| Type | When to use |
|---|---|
| Bug | Something is broken or not working as expected |
| Feature | A new capability or improvement you’d like to see |
| Feedback | General comments, impressions, or suggestions |
| Data Issue | Incorrect stats, wrong player info, missing data, etc. |
Writing Your Feedback
Section titled “Writing Your Feedback”- Title (required) — A brief summary of the issue or request, up to 100 characters.
- Details (optional) — Additional context, steps to reproduce, or explanation, up to 2000 characters.
As you type the title, the form checks for similar open issues and displays them in a yellow banner. This helps avoid duplicates — if your issue is already reported, you know it is being tracked.
Screenshots
Section titled “Screenshots”When you click the feedback button, a screenshot of the current page is automatically captured. You will see a thumbnail preview in the form. Use the Include screenshot checkbox to attach or exclude it before submitting.
Screenshots are compressed to keep submissions lightweight. If the page is too large to capture within size limits, the screenshot is silently omitted.
How Feedback is Tracked
Section titled “How Feedback is Tracked”Every submission is automatically converted into a GitHub Issue on the project repository. The backend formats the report with your feedback type, description, screenshot, and browser diagnostics (page URL, browser version, screen size, and timestamp). This means your feedback goes directly into the development backlog and can be tracked through resolution.
Submissions are limited to a handful per day per account; if you hit the cap, the form tells you and you can try again the next day.
Rate Limiting
Section titled “Rate Limiting”To prevent accidental duplicate submissions, there is a 30-second cooldown after each submission. During the cooldown, the button displays a countdown timer instead of the usual icon.