64Something is wrong, or could be better

The most reliable route is Tools → Feedback, which is there in every view mode. Below it, the description reads "Report crashes, ideas, or questions to the team", and that is the whole remit: bugs, wishes, questions, and the things that are merely annoying.

There is also a quiet line at the foot of several screens - "Have feedback or an idea? Tap here to share." It closes the Home screen, the Discover screen, the Simple View home, and the swipe-up menu in Legacy View. It opens the same form. A few places open it already named after where you were: the Assisted Features screen, the beta features list, and the beta weaving tab each carry their own invitation.

Three fields. Subject is a short line, up to 120 characters, and the counter under it shows what you have left. Email is optional and marked so; if you are signed in and Ravelry gave us a valid address, it is filled in already and you can change or clear it. Message is the part that matters, and it is the only one you must fill in.

The message box has a small formatting bar above it - bold, italic, lists, links - which writes ordinary Markdown into the text. Use it if it helps you lay out a list of steps; ignore it entirely and nothing is lost.

Tap Send at the top right. You get a toast while it goes, and "Feedback sent! Thank you for helping us improve." when it has. If it fails, it says so rather than quietly closing.

A short block of technical detail is appended to what you wrote, so that a report is answerable without a round of questions. It is the same block whether you send from the form or from a crash screen, and this is all of it:

Those recent steps are screen names and short notes the app writes for itself, such as "Screen viewed: Stash". They are not your pattern text, your notes, your photographs or your messages, and none of that is ever attached. Your email address is used to answer you and nothing else.

When something goes badly enough wrong that the screen cannot be drawn, Stash2Go shows an error screen with two buttons: Copy Error and Report Issue.

Report Issue asks one question first - "Tell us what you were doing when this happened" - and the answer is optional. Whatever you write is sent together with the crash itself and the same block of detail as above. This is the single most useful report we get, because the crash and the sentence explaining it arrive together instead of days apart.

The hardest reports to act on are the ones where nothing breaks: a screen that takes too long, a list that comes back empty, a save that does not seem to stick. For those there is Settings → Preferences → Diagnostics.

Switch Record diagnostics on, go and make the problem happen, come back and tap Send log to support. It records only what the app writes about itself, keeps the last hour, and switches itself off once the log has been sent. There is a preview of the most recent entries on the same screen if you want to see what you are sending.

The in-app form is the one that carries the technical detail, so it is the right choice for anything that went wrong. For the rest, take your pick:

Beta features especially want to hear from you. They are off by default, they are marked as beta wherever they appear, and each one has a line inviting you to say how it went. That line is not decoration - it is how a beta stops being a beta.