The future is bright!
Coming soon
There’s a few things that we didn’t get time to add into this release.
Check out the following sections to see what’s coming.
UX Design
There’s some things not quite right with the UX of the widget…
Browser Rendering of Feedback Form
Firstly, there’s a technical issue with the way that the feedback form is displayed in non-Chrome browsers. We’ve sought assistance from the makers of the core UI elements we’re using, but it might take a little while to solve.
Submission Process UX
We also don’t quite like the UX of the current feedback form submission process. Once the user click the submission button the form disappears. If the user is quick enough they can click the widget and the popup will say that the submission is processing. And after the form has been submitted it will change the popup to say it’s been submitted but once again the user needs to click the widget to see the popup.
More time is needed to consider how to better visualise this process for the user.
Widget Events
No, a widget event isn’t where all the widgets on your site get together for a big party! In geek-speak, an event is something that happens in an application that can trigger an action or set of actions to occur.
In our case there’s a couple of these events that we need to create so we can take the appropriate action.
Auto-popup
As is stands, the user needs to click on the round widget FAB button in order to bring up the feedback form.
We’d love it if you could specify a time period for the widget to wait after it’s loaded on the page, before it will automatically pop up the feedback form.
Submission Timeout
Also as it stands, once the user has submitted feedback the widget will show a “Your feedback has been submitted” message… indefinitely!
We understand that this is an important piece of functionality that really should have shipped with the first release, however, we had to draw the line somewhere!
With the way the internal logic of the widget has been programmed however, we’re confident this isn’t a massive undertaking and we already have the correct programming structures in place to allow this to happen.
Metadata Collection
As a lower priority, we’d like to add the version number of the widget release as an internal property of the widget and include the collection of metadata along with the feedback submission. This metadata should be submitted with the feedback details and include:
- The widget release version
- The widget name
- URL of the host page
- The config that was specified by the host page
- Date of submission
- History of the user’s interaction with the widget (i.e. open, close, change of rating selection etc).