Feedback That Lands Where We Work
23 September 2026
Every one of our apps has a Send Feedback screen. In our Games for Kids series, it is behind the parental gate. Today, what you type there becomes an e-mail to our support address. That works, but it puts your feedback in one place and our work in another. We plan, discuss and fix everything in an issue tracker, one for each product. A suggestion that arrives by e-mail has to be copied across by hand before it can become work, and some never make the trip.
So we are changing where feedback goes. With our next release, each message becomes a private ticket in the tracker of the app that sent it. The ticket is labeled as feedback and sits next to the crash reports and the work in progress. If you chose to include them, the device details and the app's recent activity log go with it, and those are often what let us reproduce a problem the first time. Praise is read and closed. A good idea becomes a piece of work, in the same place as everything else we are building.
The tracker is GitHub, and that raised the question we spent the most time on: what goes into it. The feedback form has an optional e-mail address, and the person typing it is often a parent writing about their child. That address does not belong in a third-party ticket system, so it never goes there. Before a ticket is filed, the address is replaced everywhere it appears: in the reply field, in the message itself if someone typed it there too, and in the activity log, in any mix of capital letters. A test fails if an address ever gets through. When you do give an address, a separate e-mail goes to our support inbox with the address and a link to the ticket, so we can answer you. When you don't, there is nobody to answer, and no e-mail is sent.
The second question was which key files the tickets. We already have an automated account that files crash reports, and it can reach every repository we have, code included. The feedback form is open to anyone, with no sign-in, so we did not want it to hold a key that powerful. Instead, feedback gets its own small app that can work with tickets and nothing else. It cannot read any code or change any settings. If its key ever leaked, the worst it could do is file tickets. It also has its own allowance of requests, so a flood of feedback can never stop crash reports from being filed.
Finally, failure. If the tracker cannot take the ticket, because GitHub is down or busy, the app tells you that the feedback could not be sent and asks you to try again later. We considered a quiet fallback to e-mail, and decided against it. A screen that says "sent" when the message went somewhere we don't look is worse than an honest error: you would assume we read it, and we would never know it existed.
None of this changes what you see on the screen. It changes what happens after you press Send: your words land where we work, and your address doesn't.
