Thanks Guy! This is great stuff. For BattCat, we’re a little past the point of being able to make significant changes, as our development time has moved on to the next bit of work. But this is really valuable feedback and something we can definitely take into account for next time.
For now, I can offer some context around why we made the choices we did.
For the ‘poor data’ vs ‘other’ question…
The theory is that ‘other’ should be used when the problem or next step can be identified, but we don’t have an option for it. This will allow us to go in manually at the end, look at ‘other’ devices and pull out any battery issues we missed when designing the quest.
On the other hand, we know from previous quests that much of the data recorded lacks the detail needed to classify it properly. It’s a fairly well documented problem at this point, so our focus here is very much on battery issues as supposed to data issues. We also wanted to make the task as simple as possible, as feedback from those previous quests suggests that they’ve sometimes been too confusing in the past.
Of course, we’d love to help repair groups record more info for each repair at events to minimise this problem in future 
Being able to select device categories is a really interesting suggestion. For power-questers, such as yourself 
, I can see how that could be useful. We can certainly keep that in our back pocket for any future quests we build.
Funny you should mention the search feature. We did go through a similar process when putting the quest together, e.g. getting rid of all the devices with one-word descriptions and various other common, but unhelpful, phrases. Perhaps we should have excluded the ‘won’t/doesn’t charge’ entries too. Good lesson for us 
Thanks again Guy, and if you’d like to dive in again, I’m running an online social event where we’ll all have a go together. It would be great to have someone who already knows the drill there!