The team is worried about hidden friction in LocalLens. Start from a fresh account if possible, move through search, messaging, trust copy, and capture the first moment where the product stops feeling obvious. Use NVDA screen reader / Windows, MacBook Air M2 / Chrome, Ubuntu / Firefox and Low bandwidth 4G profile.
What to check
01
Accessibility and trust pass
1. Open LocalLens
2. Complete search
3. Stress messaging
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 trust copy
3. Compare behavior on another required device
4. Record bugs and UX friction separately
Open the app →launch-seed.qahuman.dev/apps/locallens?job=055
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 $220 job would be $198.