What to do:
You are testing Foomchat for sign-in usability, UI issues, and overall ease of use. Follow these steps:
Landing Page: Open https://foomchat.com. Note your first impressions β is the purpose of the app immediately clear? Is the layout clean and intuitive?
Sign-Up: Create a new test account using credentials you control (do not use any personal or production accounts). Note how smooth and clear the sign-up flow is. Report any confusing steps, error messages, or UI glitches.
Sign-In: Sign out if you are automatically logged in, then sign back in with your test account. Note how easy the sign-in process is, any friction points, and whether error states (e.g., wrong password) are handled clearly.
Core App Experience: Once signed in, explore the main features of the app. Try to understand what the app does and how to use it. Note whether the UI is intuitive and whether the app's purpose and features are easy to grasp.
General UI: Look for any visual bugs, broken elements, unclear labels, confusing navigation, or anything that feels off or incomplete.
Report on:
Clarity of the app's purpose from the landing page
Ease and clarity of sign-up and sign-in flows
Any bugs, errors, or UI issues encountered (with timestamps in your recording)
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 512 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $10.00 is released per accepted submission.
Tester requirements:
Desktop Safari browser (macOS)
Create and use a tester-controlled test account for sign-up and sign-in β do not use personal or production credentials
What you must do to be paid
Before you apply
Access to a device that can open https://foomchat.com/
Desktop Safari browser (macOS)
Create and use a tester-controlled test account for sign-up and sign-in β do not use personal or production credentials
You are testing Foomchat for sign-in usability, UI issues, and overall ease of use. Follow these steps:
1. **Landing Page**: Open https://foomchat.com. Note your first impressions β is the purpose of the app immediately clear? Is the layout clean and intuitive?
2. **Sign-Up**: Create a new test account using credentials you control (do not use any personal or production accounts). Note how smooth and clear the sign-up flow is. Report any confusing steps, error messages, or UI glitches.
3. **Sign-In**: Sign out if you are automatically logged in, then sign back in with your test account. Note how easy the sign-in process is, any friction points, and whether error states (e.g., wrong password) are handled clearly.
4. **Core App Experience**: Once signed in, explore the main features of the app. Try to understand what the app does and how to use it. Note whether the UI is intuitive and whether the app's purpose and features are easy to grasp.
5. **General UI**: Look for any visual bugs, broken elements, unclear labels, confusing navigation, or anything that feels off or incomplete.
**Report on:**
- Clarity of the app's purpose from the landing page
- Ease and clarity of sign-up and sign-in flows
- Any bugs, errors, or UI issues encountered (with timestamps in your recording)
- Overall intuitiveness and learnability of the app
- Any specific moments of confusion or delight
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot. Speak your findings aloud while recording whenever you can: narration is strongly encouraged and makes your report far more useful, but it is not required and a quiet recording will still be reviewed on its merits.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
β’
Access to a device that can open the target URL
β’
Report every issue with a severity and exact reproduction steps
β’
Only submit evidence you captured yourself during this run
β’
Desktop Safari browser (macOS)
β’
Create and use a tester-controlled test account for sign-up and sign-in β do not use personal or production credentials
SKILLS NEEDED
Desktop Safari browser (macOS)Create and use a tester-controlled test account for sign-up and sign-in β do not use personal or production credentials