Feedback

Every product decision since v1.0.0 has been shaped by user feedback. Keep it coming.

How to send feedback

1. In-app feedback prompt (preferred)

After you've generated a few proposals, the Extension shows a small feedback prompt. Click "Not really" and type your message. This is the best channel because:

The prompt is gated to appear only when you're not in an active generation flow, and you can dismiss it permanently if you don't want to see it.

2. Email

support@approidtech.com with [feedback] in the subject line.

Same destination as the in-app prompt, but useful when you want to attach screenshots or have a longer conversation.

3. Chrome Web Store review

Leave a review on the Web Store. Reviews help other freelancers find the Extension, and we read every star rating + comment. We can't respond to reviews directly, but if you mention an issue we'll often ship a fix and reply in the next changelog entry.

What kind of feedback helps most

In rough order of usefulness:

  1. Specific bugs you can reproduce. "When I do X on Y page, Z happens. I expected W." We can fix what we can verify.
  2. Friction in real workflows. "I open the panel, hit Detect, but I have to click three things before I can generate." Tells us where the UX is wasting your time.
  3. Output quality complaints with examples. "This proposal it generated for [job type] sounds AI." Paste the proposal text. We tune the prompt against real failure cases.
  4. Feature requests with context. "I'd want X because I do Y a lot." The "why" is more useful than the "what" — it lets us solve the underlying need, sometimes in a different way.
  5. General comments. "Love it, here's what works for me." Encouraging and useful for prioritisation, even though they don't generate immediate work.

What we do with feedback

What we won't do with feedback

The diagnostic data attached to in-app feedback (user agent, plan, generation count) is described in our Privacy Policy.

Contact

support@approidtech.com — every reply is from a human.