Currently, we lack insights into why users deactivate our plugin. To address that, we could display a modal that asks for feedback when users choose to deactivate the plugin.
By gathering user feedback, we can better understand the reasons behind deactivation and use these insights to improve the plugin through bug fixes and future enhancements.
We’ll introduce a modal containing the following components:
A list of reasons for deactivation with the following options:
I no longer need the plugin
I found a better plugin
It’s missing a feature I need
I couldn’t get the plugin to work
It’s a temporary deactivation
Other
A textarea for users to provide additional comments
Two buttons:
"Send feedback & deactivate" - When clicked, we’ll send the feedback along with the plugin version, PHP version, and WordPress version to our API, then proceed with deactivating the plugin
"Skip & deactivate" - When clicked, we’ll immediately deactivate the plugin without sending any data to our API
A few key points to keep in mind:
To maintain the plugin’s lightweight nature, avoid including any third-party libraries for the modal. Utilize native browser elements and/or Web APIs or features built into WordPress (for example, the <dialog> element, caniuse ref).
Ensure that giving feedback is entirely optional for users. They should always have the choice to skip the feedback part and proceed with the deactivation directly.
Only collect the essential information required for feedback purposes. That includes the selected reason for deactivation, any comments provided by the user, as well as the plugin version, PHP version, and WordPress version. Do not collect any other data related to the user’s website to respect their privacy. When a user chooses to skip the feedback part, do not send data to our API altogether.
If there are any issues with sending feedback to our API, such as networking problems or the API being down, do not hinder the deactivation process. Instead, gracefully handle any errors without displaying error messages to the user or preventing them from deactivating the plugin. The deactivation process should remain smooth and uninterrupted, regardless of any data transmission issues that may arise.
over-engineer
commented
1 year ago
Currently, we lack insights into why users deactivate our plugin. To address that, we could display a modal that asks for feedback when users choose to deactivate the plugin.
By gathering user feedback, we can better understand the reasons behind deactivation and use these insights to improve the plugin through bug fixes and future enhancements.
We’ll introduce a modal containing the following components:
A few key points to keep in mind:
To maintain the plugin’s lightweight nature, avoid including any third-party libraries for the modal. Utilize native browser elements and/or Web APIs or features built into WordPress (for example, the
<dialog>element, caniuse ref).Ensure that giving feedback is entirely optional for users. They should always have the choice to skip the feedback part and proceed with the deactivation directly.
Only collect the essential information required for feedback purposes. That includes the selected reason for deactivation, any comments provided by the user, as well as the plugin version, PHP version, and WordPress version. Do not collect any other data related to the user’s website to respect their privacy. When a user chooses to skip the feedback part, do not send data to our API altogether.
If there are any issues with sending feedback to our API, such as networking problems or the API being down, do not hinder the deactivation process. Instead, gracefully handle any errors without displaying error messages to the user or preventing them from deactivating the plugin. The deactivation process should remain smooth and uninterrupted, regardless of any data transmission issues that may arise.