Mobile Feedback

It was the first thing our new hires tripped over. Even shipping it behind a flag would let us validate the approach.

Leaks the previous org's data into the picker — reproduced on two machines. Expected: the public site keeps its state. Actual: it silently truncates long titles.

Ignores the sort order on mobile — reproduced on two machines. Expected: the keyboard shortcuts keeps its state. Actual: it shows a stale vote count until a hard refresh.

We would stop exporting to a spreadsheet every Friday. A rough first version would already be a big improvement. What we would need: Custom domains MRR-weighted prioritisation An…

Right now this costs us roughly two hours a week. We are working around it with a spreadsheet, which is not sustainable. What we would need: Post templates Bulk actions A public…

Even shipping it behind a flag would let us validate the approach. It would cut a full step out of our triage loop. Not urgent, but it would save everyone about an hour a week.…

Not urgent, but it would save everyone about an hour a week. It would cut a full step out of our triage loop. We raised this during the pilot and it is still the main gap.

It was the first thing our new hires tripped over. This is table stakes in every competing product we evaluated.