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

Results / end of experiment usability #238

Open
vincentadam87 opened this issue Sep 15, 2014 · 9 comments
Open

Results / end of experiment usability #238

vincentadam87 opened this issue Sep 15, 2014 · 9 comments

Comments

@vincentadam87
Copy link
Contributor

When the 30 days are over

  • Results are availble -> loaded into a webview from outside of the app

Show we

  • give a link and pass (or social login) to access results from any browser (not only the phone)
  • let the user continue the app (and results could be computed live on server on all the available data)
  • let the user pause the app: keep it installed, results accessible from dashboard but no more probes/daily questionnaires

@wehlutyk @MklBst

@wehlutyk
Copy link
Member

  • give a link and pass (or social login) to access results from any browser (not only the phone)

We don't have time to do this straight away. It would be nice in the near future though.

  • let the user continue the app (and results could be computed live on server on all the available data)
  • let the user pause the app: keep it installed, results accessible from dashboard but no more probes/daily questionnaires

I'd say both. For now it's only option 1, and I'm not really excited at adding new features before release at ECCS, but it definitely come in an update.

I'm setting this issue as "ECCS optional", but we can continue the conversation.

@wehlutyk wehlutyk added this to the ECCS optional milestone Sep 15, 2014
@vincentadam87
Copy link
Contributor Author

Yes, no worries
The good thing is that the webview gives us a month to think about some results, and we don't have to code in java anymore

@wehlutyk
Copy link
Member

:-). Exactly why I love this WebView. Javascript to the rescue!

@MklBst
Copy link
Contributor

MklBst commented Sep 16, 2014

A link to an external page indeed sounds great. And yeah, probes continue !

@wehlutyk
Copy link
Member

Decision time. I suggest:

  • Add a "Pause" (or "stop") button to stop probes once the 30 days are over. The user can still see his results.

Problem: if the user wants to restart, questions will probably have evolved since. It would be a pity to lose a potential recurrent user by feeding him the same questions each time he wants to restart. So the button can change to "restart" and it'll reset the experiment (a bit like the "reload parameters" button in test mode).

Problem 2: the user then loses all the information from the previous times he did the experiment. For this we need the login mechanism, and the user can browse his past experiments on the website (aaaaargghhh implementation!).

@wehlutyk
Copy link
Member

Login: #324.

@MklBst
Copy link
Contributor

MklBst commented Sep 26, 2014

I don't know:

  • if the participant wants to continue: the app is here to probe.
  • if the participant does not want to continue, she uninstalls it: once the results have been assessed, and possibly shared / downloaded. Maybe just a message: if you leave us, we'll forget about you!

reloading of parameters is a problem per se #325

@wehlutyk wehlutyk modified the milestone: 0.26 Oct 3, 2014
@MklBst MklBst modified the milestone: International Release Oct 10, 2014
@vincentadam87
Copy link
Contributor Author

So there was no decision here.
A stop button or only stop at uninstall?

  • If login, we do not need a pause
  • If pause button, where to put it?

@wehlutyk
Copy link
Member

I'd say: add a "stop probes" button under the "Days elapsed" once results are available. The button turns into a "restart exp" once clicked. And clicking that does the same as "reload parameters" in test mode (keeps profile, but reloads questions and resets all the rest).

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

No branches or pull requests

3 participants