A bug, an idea, or just a hello — all of it is welcome.
Riff Quest is built by a very small team, so there is no ticket queue and no support bot standing between you and the person who wrote the code. Every message lands with someone who can actually change the app, which is why a clear bug report can turn into a fix in one of the next releases rather than sitting in a backlog for a quarter.
The fastest route, and the right one for anything that needs back-and-forth: screenshots, clips and follow-up questions all stay in one thread. Bug reports and feature requests are read here every day.
Join the server →Better for longer messages, anything you would rather not post in public, and partnership or press enquiries.
mjablonskidev@gmail.com →Most bugs in a practice app are situational: they depend on the browser, the audio device, the exercise you were in, or the state your session was in when things went sideways. The more of that context arrives with the report, the less time gets spent reproducing it. A single sentence plus a screenshot is usually enough.
Ideas posted in Discord get read and discussed in the open, and the ones that keep coming up from different players tend to get built first. Plenty of what the app does today started as somebody complaining that practising a scale felt like homework, or that they could not tell whether a week of practice had actually gone anywhere. Telling us the problem you have is more useful than describing the feature you think would solve it, because the problem is the part we cannot guess.
Questions about scoring, streaks, Fame, note detection setup or the desktop app usually have a written answer already. The frequently asked questions cover the short versions, the knowledge base explains every screen in detail with screenshots, and the practice guides deal with routines, session length and progress tracking rather than the app itself.