Testing notes wanted for TutorTrail:
1. What broke in onboarding?
2. What felt unclear in progress tracking?
3. What edge case appeared in file upload?
4. What should we fix before launch?
Devices to cover: Ubuntu / Firefox, Low bandwidth 4G profile, Windows 11 / Chrome + Edge, Steam Deck / SteamOS.
What to check
01
Core happy path
1. Open TutorTrail
2. Complete onboarding
3. Stress progress tracking
4. Try a negative or edge path
5. Summarize whether this feels ready for real users
02
Returning user pass
1. Return after a simulated break
2. Use file upload
3. Compare behavior on another required device
4. Record bugs and UX friction separately
Open the app →launch-seed.qahuman.dev/apps/tutortrail?job=037
It shows what a real brief looks like. When a founder funds a job like this, you pitch here: a couple of lines on what you'd test, your price and your hours. The pay on a $120 job would be $108.