ARADAR is a small product, built by a small team. Every message you send reaches the person building the software.
The fastest way to reach us is email. We read everything and reply to most things within a day or two.
What to send
Anything that would help us make ARADAR better.
- Bug reports. What you were doing, what you expected, what actually happened. Screenshots help more than words. If the app crashed, the ARADAR version (from ARADAR → About) and your macOS version give us most of what we need to reproduce.
- Feature requests.The workflow problem you’re trying to solve is more useful than a proposed solution. We’d rather hear “I can’t tell at a glance which of these 50 references are unrated” than “add a column to the library table”.
- Producer workflow notes. Tell us how you actually use ARADAR day-to-day. Every major feature in the app started as a real workflow problem; the next one might start with yours.
- Praise. If something in ARADARsaved you time on a track, tell us. We’re building this between studio sessions and feedback is most of the fuel.
Other channels
For license questions (replacing a key, freeing an activation slot, refunds) the same address works: hello@aradar.app. You can also browse the help reference or the license FAQ for answers to the questions we hear most often.
For security disclosures, please email hello@aradar.app. The /.well-known/security.txt at the apex contains the full coordinated-disclosure terms.
Thanks for taking the time. We don’t take it for granted.