You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to update our user registration and notification flow to accomplish these goals:
Allow listeners to sign up for notifications
Create an account on the site so listener-submitted detections are credited to them
Request survey information for the UX team to make improvements with. (Though I don't have any insights into what the UX team would like to find out - should this be optional? And should the questions be updated?)
Accept the minimally necessary information in steps to avoid information overload
"Get Notified" button opens a modal or a new page with just an email field (and UX participation opt-in)
On email submission, we suggest adding a password/password confirmation and username for account creation
We then link to an optional survey for whatever questions the UX team is looking to have answered
We send them to the feeds list page to listen or create a user dashboard for people to track their detection submissions and fill out the survey if they haven't already.
Some other questions:
Should we have a separate flow that doesn't include signing up for notifications? How/where do they access that flow?
The text was updated successfully, but these errors were encountered:
Hi,
I want to provide an update from the Notification team regarding our research on the signup form. We've actively engaged users to gather insights on the signup form requirements. Currently, we're in the process of developing the wireframe for the signup form and will soon proceed with usability testing.
Here are some key findings from our research:
Users prefer the signup form to be straightforward to use.
Users suggested making the form more visually appealing.
Users would prefer if the form did not redirect them to another platform.
Some users found the Whale Wise guideline confusing, as it did not provide information directly within the form.
We are happy to share our design input in detail if required.
We would like to update our user registration and notification flow to accomplish these goals:
Currently, our notification subscription flow looks like:
We also have a separate user registration and sign-in form that isn't directly linked anywhere (yet): https://live.orcasound.net/register
One potential flow could look like:
Some other questions:
The text was updated successfully, but these errors were encountered: