HabitHarbor is ready for an outside set of eyes. Run the core flow, test negative paths around offline states, and flag anything that hurts trust, completion, or perceived quality. Evidence and repro clarity matter more than bug volume.
What to check
01
Accessibility and trust pass
1. Open HabitHarbor
2. Complete offline states
3. Stress onboarding
4. Try a negative or edge path
5. Summarize whether this feels ready for real users
02
Device-specific check
1. Return after a simulated break
2. Use settings
3. Compare behavior on another required device
4. Record bugs and UX friction separately
Open the app →launch-seed.qahuman.dev/apps/habitharbor?job=035
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 $65 job would be $58.50.