Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate new registration and notification subscription flow #333

Open
Tracked by #303
skanderm opened this issue Feb 5, 2024 · 1 comment
Open
Tracked by #303

Investigate new registration and notification subscription flow #333

skanderm opened this issue Feb 5, 2024 · 1 comment
Assignees
Labels
needs: design input Needs design or UX work before ready to work on needs: discussion Discussion needed before ready to work on

Comments

@skanderm
Copy link
Contributor

skanderm commented Feb 5, 2024

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

Currently, our notification subscription flow looks like:

  1. "Get Notified" button in the header of live.orcasound.net
  2. Redirect to a Google Form for notification sign-up and survey questions
  3. On submission of the Google Form (with required email), the listener is subscribed to email notifications through an API call from the Google Form.

We also have a separate user registration and sign-in form that isn't directly linked anywhere (yet): https://live.orcasound.net/register

Image

One potential flow could look like:

  1. "Get Notified" button opens a modal or a new page with just an email field (and UX participation opt-in)
  2. On email submission, we suggest adding a password/password confirmation and username for account creation
  3. We then link to an optional survey for whatever questions the UX team is looking to have answered
  4. 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?
@skanderm skanderm added needs: discussion Discussion needed before ready to work on needs: design input Needs design or UX work before ready to work on labels Feb 5, 2024
@skanderm skanderm modified the milestone: v3 Feb 5, 2024
@sonamchauhan1201
Copy link

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.

Sonam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: design input Needs design or UX work before ready to work on needs: discussion Discussion needed before ready to work on
Projects
Status: idea
Development

No branches or pull requests

3 participants