64Something is wrong, or could be better

The surest way in is Tools → Feedback, which is there in every view mode. The line under it reads "Report crashes, ideas, or questions to the team", and that really is the whole of it: 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. In a few places the form arrives 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 boxes. Subject is one short line, up to 120 characters, and the counter under it shows how many you have left. Email is optional and says so. If you are signed in and Ravelry gave us a working address, it is filled in already, and you can change it or clear it. Message is the part that matters, and it is the only one you have to fill in.

Above the message box is a small formatting bar: bold, italic, lists, links. It writes ordinary Markdown into your text. Use it if it helps you lay out a list of steps. Ignore it and nothing is lost.

Tap Send at the top right. A short message shows while it goes, then "Feedback sent! Thank you for helping us improve." when it has arrived. If it fails, it says so rather than quietly closing.

A short block of technical detail is added to what you wrote, so a report can be answered without a round of questions first. 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. None of that is ever attached. Your email address is used to answer you, and for nothing else.

When something goes wrong badly enough 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". You do not have to answer it. Whatever you write is sent along 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.

Turn 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 gone. On the same screen you can see a preview of the most recent entries, if you want to know what you are sending.

The form in the app 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 start off, 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.