Today I shipped an important fix to the 8BitDo buying assistant.
I underestimated the importance of accessibility. Some controllers were labelled with 'accessibility' but it wasn't exactly clear what that meant.
Now people can answer 'Do you need accessibility-focused options?' directly. I came across a user on BlueSky who wrote about triggers causing too much strain. 8bitdo developed a solution for that. You can flip between how a normal trigger behaves and a more 'clicky' experience, essentially forcing it to behave like a normal button.
I now map both data sources:
features.modeSwitchcontrollerMode: "Trigger Mode Switch"
as one canonical feature and treat it as accessibility-relevant for filtering.
Buyers who are not specialists often describe needs in plain language. It's my job to map their experience to whatever features controllers offer. The picker should translate that intent into correct product matches.
Next step is to expand the accessibility bucket with more signals, one by one, and keep the question simple for non-technical shoppers.