Threads instead of an email flood
Every topic has its own thread. New posts are announced by email, with a subscription per thread. Finished topics move to the archive and can still be read.

backend
A closed area for the testers of my audio plugins. Builds, feedback and known bugs end up here instead of in lots of separate emails.
All images show the real interface with sample data.
Every topic has its own thread. New posts are announced by email, with a subscription per thread. Finished topics move to the archive and can still be read.

Posts with Markdown, attachments and reactions. Each name shows the tester’s system and DAW, so a bug can be placed right away. From any post I can write to the tester directly.

The text on the left, on the right how it will look. Images can be dragged straight in or pasted from the clipboard.

Invitation links with an expiry date and a limited number of uses. I approve every sign-up myself.
One message to all testers, with a test email first and a history of earlier broadcasts.
Testers appear with their name and studio in the plugin credits. Anyone who would rather not can untick it in their profile.
emails
Every tester chooses which threads to follow and can unsubscribe from any of them with one click. All emails go through the same frame as the support emails and newsletter of Ohlhorst Digital.
| when | email to |
|---|---|
| someone signs up | me, for approval |
| I approve someone | the new tester |
| a new thread starts | all testers, if ticked when it is created |
| a reply comes in | everyone subscribed to the thread |
| I write a broadcast | all testers |
| I write about a post | the tester. Their reply comes straight to me. |
