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

Landing page before Consent #1337

Open
BeritJanssen opened this issue Oct 31, 2024 · 1 comment
Open

Landing page before Consent #1337

BeritJanssen opened this issue Oct 31, 2024 · 1 comment

Comments

@BeritJanssen
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
At the moment, if a Consent form is attached to an Experiment, it will always get shown first when a new participant arrives on the page. The TuneTwins team requested that it would be possible to show a page before this, with information about the reasoning and team behind the game.

Describe the solution you'd like
This could be implemented without extra development time by referring participants to a blog post with relevant information on the Amsterdam Music Lab website.

Describe alternatives you've considered
Having a landing page within MUSCLE could still have its merits, though: imagine an Experiment that has one Block that starts immediately with Autoplay. If we have a returning Participant, i.e., they don't get the Consent form, they would not get to hear the audio because the required user interaction is missing. The landing page could provide the extra click needed to get the Autoplay to work. Still, this is a bit of an edge case, and doesn't actually apply for the MatchingPairs game.

@BeritJanssen
Copy link
Collaborator Author

BeritJanssen commented Nov 12, 2024

I just discussed with @Lia-JX-Li , and the advantages of a landing page over a blog post would be:

  • there is only going to be one URL that will be communicated with participants, rather than the AML website and the experiment link
  • participants won't get distracted by the AML homepage, where they may potentially end up elsewhere by clicking on other content

I was just thinking that perhaps we could use the aboutContent field to populate an HTML page with information. Then, the sharing link would be app.amsterdammusiclab.nl/my-awesome-experiment/about. That also wouldn't show consent. Clicking on a button in the about page will take the participant to the experiment proper, and the consent page. If participants share the experiment with each other, we can make sure they share the about page by adjusting the link through the admin interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants