We will likely be able to do 1 round of evaluative research and we should use it to test as many assumptions and variants as possible. Let's define what those look like and then create/prioritize tasks accordingly.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Jhernandez | T148358 Prepare for November user research | |||
| Resolved | None | T148364 Complete Quickfact prototype for testing | |||
| Declined | • atgo | T148381 Define variants of Flashcard prototype for testing |
Event Timeline
Comment Actions
Variant 1
- Variant 2 on it's way
- CSS is on it's way
- These pdfs are not optimized, they are pretty large due to non optimized images and extra metadata
cc @atgo
Comment Actions
Variant 2 details
- Dark theme
- no "flashcard" branding
- different typography
- small image, text first
^ @atgo need to fill this in..
Comment Actions
@atgo if I'm not getting it wrong, we want to test different variations of flashcards?
to create the variations, we need to define the what differences we want to test. do we have a list of differences or is it based on design's judgement?
Comment Actions
@Nirzar closing the loop here - variants are based on design's judgement as we discussed a while back. If there's nothing we need to test, let's close this.