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

Grayed out play button is confusing to users #334

Closed
4 tasks
Tracked by #648
Filadora opened this issue Feb 6, 2024 · 2 comments · Fixed by #675
Closed
4 tasks
Tracked by #648

Grayed out play button is confusing to users #334

Filadora opened this issue Feb 6, 2024 · 2 comments · Fixed by #675
Assignees
Labels
needs: investigation Needs to be debugged or reproduced type: bug Something isn't working

Comments

@Filadora
Copy link

Filadora commented Feb 6, 2024

Users were confused with the play button. It is disabled before the user chooses a hydrophone and after the hydrophone is chosen there is a need to click on it. This two-step flow confused users and made them think that something was not working properly (either hydrophones or a play button).

Possibly that is a bug (according to Paul).

Screenshot 2024-02-06 at 4 13 37 PM

Tasks

Preview Give feedback
  1. type: improvement
    paulcretu
  2. needs: discussion
  3. type: improvement
    skanderm
@Filadora Filadora added the type: bug Something isn't working label Feb 6, 2024
@github-project-automation github-project-automation bot moved this to triage in Orcasite Feb 6, 2024
@paulcretu paulcretu added the needs: investigation Needs to be debugged or reproduced label Mar 5, 2024
@paulcretu
Copy link
Member

I've tried to reproduce this on desktop and mobile (Chrome and Firefox), and I can't get the exact same behavior. I can confirm that the play button is grayed out before a location is selected (which is expected), but my audio always seems to autoplay once I select a location.

I agree that the grayed out play button might be confusing. My thought was to remove the bottom player bar completely when nothing is selected (see #232), but happy to discuss other solutions.

@adrmac adrmac mentioned this issue Oct 3, 2024
@adrmac
Copy link
Member

adrmac commented Oct 4, 2024

I agree this issue is a priority. In analytics, we can see a lot of drop off (70%) with new users coming to the home screen but never starting the player. Going from the "Listen Live" call to action on the orcahome site, there are 3 clicks required to get to an audio stream:

  1. Listen Live
  2. Home: Select a hydrophone
  3. Listen: Select a hydrophone
  4. Hydrophone auto-starts after selection

I believe users are dropping off on step 2. Here are three ideas to resolve this:

  1. Hide player bar on the Home screen (Paul's proposal)
  2. Link the Listen Live button directly to the Listen screen (simplest, maybe good to test), and/or consolidate Home and Listen into one screen
  3. Have the live.orcasound.net URL default to Orcasound Lab for new users, or most recently opened player for returning users (no autoplay), or most recent verified whale detection

How do we know if we are successful in resolving this?
We should see the number of player starts rise as a % of site visits.

@adrmac adrmac changed the title Play button (autoplay) Grayed out play button is confusing to users Oct 4, 2024
@github-project-automation github-project-automation bot moved this from triage to done in Orcasite Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: investigation Needs to be debugged or reproduced type: bug Something isn't working
Projects
Status: done
Development

Successfully merging a pull request may close this issue.

3 participants