🗳️ Proposal: Lightweight In-App Feedback Toasters

[aliana-org]

🗳️ Proposal: Lightweight In-App Feedback Toasters

Hello everyone,

To help us collect feedback faster and more directly, we're considering introducing a lightweight in-app feedback system. The goal is to gather insights without disrupting your workflow.

💡 How It Works

• After you've used a feature for the first, third, or fifth time, a small toaster would appear asking for your feedback.
• The toaster would simply ask whether your experience with the feature was good or bad — using a 👍 or 👎.
• After responding, you’d see a short thank-you message and be given two options:
  • Fill out a short feedback form
  • Start a discussion here on GitHub (for quick thoughts or ideas)

Both thumbs up and thumbs down would trigger the same follow-up, just with different messaging depending on your response.

🔐 Privacy & Data

• The number of times you've used a feature is counted locally on your device.
• No server requests are made for this.
• Even when you click 👍 or 👎, no data is sent to our servers — it's purely a local prompt to encourage feedback.
• In short: clicking thumbs up or down does not do anything "behind the scenes."

This may change in the future, but if it does, we’ll be transparent about how and why.

🧪 Future Ideas

We don’t want to stop with just this kind of toaster. Some other ideas we’re exploring:

• A feedback prompt after encountering an error, asking whether you'd like to report it
• Contextual toasts based on certain usage patterns

🙋‍♀️ We Want Your Input

Please let us know what you think! Do you like the idea of this kind of lightweight feedback system?

React with a 👍 or 👎 to vote on whether we should implement it.

We’ll stay out of the voting — this one’s up to the community.
If you have suggestions, better ideas, or concerns, feel free to leave a comment below.
Thanks!

[aliana-org]

📣 Clarification on Feedback Prompts, Privacy & A/B Testing

Thanks for the interest! Here's some more detailed information about how the feedback prompt system works in the modcore Extension Manager, especially regarding privacy and A/B testing.

---

❌ Why We Don’t Collect 👍 or 👎 Responses

We do not collect any thumbs-up (👍) or thumbs-down (👎) responses because:

• It would require a backend server to receive and store the data.
• We intentionally avoid using servers for such use cases to keep the project lightweight and privacy-respecting.
• This is an open-source project, so any server-side logic (like webhooks) would be publicly visible — which limits what we can securely or reliably do with remote data.

---

⚙️ Feedback Prompt Settings

We will provide a Settings section to give you full control over the behavior of feedback prompts. The settings will include:

• ✅ Enable or disable feedback prompts entirely.
• ⏱️ Customize when prompts appear (optional):
  e.g., after X feature uses, after Y days, etc.
  You can reset to the default behavior at any time.
• 📥 Download your local feedback data:
  The extension will track (locally):
  • How often you gave a thumbs up/down
  • How many times the prompt was shown
    You can choose to manually share this file with us, if you wish — no automatic sharing.

🔐 Important: All of this data is stored locally and is never sent anywhere unless you choose to share it manually.

You can also disable local data collection entirely, which will automatically disable the download feature as well.

---

❎ Closing Prompts

Don’t want to give feedback? No problem.
All feedback prompts will include a small ❌ close button and can be dismissed easily without interaction.

---

🧪 Local A/B Testing: How It Works

To ensure the feedback system is genuinely useful and non-intrusive, we’ll roll it out using a simple local A/B test:

• On installation, each user is randomly assigned to Variant A or Variant B.
• This assignment is stored in your browser’s localStorage and can be changed manually if you wish.

Variant Behavior:

• Variant A: Feedback prompts are disabled by default.
• Variant B: Feedback prompts are enabled (based on default usage triggers).

This lets us understand the impact of the prompts while respecting user privacy and avoiding external tracking.

---

If you have any suggestions or concerns, feel free to open an issue or join the discussion!

Thanks for helping make modcore better 🙌