Features

Currently, the ShakePicker dropdown component defaults to a value. My requested change would introduce the following: Not selecting a default value Requiring users to select a value I'm requesting this as an optional prop to the component. Or alternatively: Adding an invalid: boolean prop to shakePickerItem that means users can't submit a Shakebugs form without selecting something else My use-case is around requesting users give some context around where the bug exists, so we can route to teams. We want to force users to make an active choice, which is currently impossible with the current shakePicker dropdown. I'm happy to expand on my request here or offer more concrete ACs if the team is interested! It should be low hanging fruit and relatively easy to implement, imo!

We would like to have crash reporting on React Native.

Instead of typing a description, users could record their voice instead. Why I think this matters: Capture in the moment Often when using the app, users notice things they want to flag Taking time to type detailed feedback breaks the flow Voice would let them capture thoughts immediately and naturally Richer context Voice allows for more nuanced explanation of issues Easier to explain user journey/context verbally Implementation thoughts Could start simple: basic voice recording + transcription Transcription would replace the description and recorded audio would be sent as an attachment

Give the option to customize the email domain and have the option to enable/disable this feature.

We would to optimize our template and force users to fill fields that for us are necessary to resolve issues Example: add a list of our features and force user to chose one when an issue is raised

A lot of tags were created for old features, by mistake, etc... We want to be able to clean the list of tags easily

We want a solution that offers both bug reporting and crash reporting for Flutter.

In the built-in chat feature on our website, replies to client messages currently lack any visible context or reference to the original query. This can cause confusion for clients, as they may not remember the issue they initially contacted us about.

As someone taking on ownership of implementing Shake, I want to be able to use the data that comes out of it to help inform answers to various questions that we have as a team. We then use a data ingest pipeline for the various tools we have and pipe this data to a data warehouse like Google BigQuery. Bi-directional would be nice as well — so we could change the status, assignee, etc of a report. Add-on comment: Maybe a Google Data Studio integration / connector (like Ahrefs has).