Tester feedback guide
What we want eyes on, how to report things you find, and the severity language we use so we know what to fix first.
What we want eyes on
You're not a free QA — you're a domain expert. The most useful feedback is about whether Stackd actually works for the way real trainers work. A few specific things we're listening for:
Workflow friction
"I had to click X to do Y, and that felt weird." Specific moments where the app made you stop and think are gold — they usually mean the model is off, not just the UI.
Things that should exist but don't
Tell us what's missing. "I expected a way to bulk-message all clients" is way more useful than "messaging is missing features." Specifics beat generalities.
Aesthetic / brand fit
Does it feel like a tool you'd actually pay for and put your clients in front of? Anything that feels off — wrong tone, ugly state, awkward empty screen — tell us.
Surprises during real client work
If you used Stackd with a real client this week and something surprised you (in a good or bad way), that's exactly the moment we want to hear about. Even small things — "the report PDF looked better than I expected" is useful.
How to report
The fastest path is text + a screenshot. Send to trevor@stackd.app with a subject line including a rough severity tag (see below).
What to include
- What you were trying to do — the goal, not the click path.
- What happened vs. what you expected.
- Steps to reproduce — even rough ones. "I think I clicked Programs then ..." is fine.
- Screenshot or short screen recording — Loom is great, but a single screenshot is plenty.
- Browser + device — Chrome on Mac vs. Safari on iPhone behave differently. We need to know.
Severity language
Blocker — I can't do real work right now
App won't load, data loss, can't log in, can't message a client during a session. Drop everything and tell us — we'll roll back if needed.
High — workaround exists but it's painful
A core flow breaks halfway and forces you to start over, but you can finish the task another way. Same week fix.
Medium — wrong behavior, but not blocking
Wrong number on a dashboard, weird modal behavior, calculation looks off. Fixed in normal cycle.
Low / polish — looks weird, copy is off, alignment
Typo, ugly state, color seems wrong, animation is jerky. Batched and fixed in polish rounds.
Suggestion — could be much better if…
Not a bug — a "this would be 10× better if" idea. These shape the roadmap. Send them.
Bonus: things we already know about
- Long-idle Realtime can miss messages — refresh fixes it.
- Apple Health import is not wired up.
- Calendar sync (Google/Apple) is not wired up.
- Video uploads in messages are not implemented (text only).
If you find something here that isn't in this list, it's worth reporting.