You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussion with @philhewinson lead to some ideas around gamification. Perhaps the best of these is a format inspired by Who Wants to Be a Millionaire?:
Multiple (but finite) levels. At each level, the user is prompted to select their favourite, or rather which they think is the most popular glyph from a particular emoji. If they choose correctly they move to the next level. Difficulty of levels can be calculated by variance in glyph_score.
Big problem with this approach: all the data (i.e. answers) are available on the emoji pages.
The text was updated successfully, but these errors were encountered:
Further discussion led to some ideas I really like.
Remove the results page entirely (currently only 74/3061 hits are on /results/*), and replace the vote page with two glyphs from the same set. User is now required to choose their favourite, and if they get the "correct" one they move to the next level (as above), otherwise they are back to zero.
Votes are now in pairs (ie we need to know which pair took which vote), meaning each emoji is like a mini-league.
Should result in a more addictive behaviour from the user, only two glyphs makes it very fast to play, and seeing the score tick up will keep users engaged.
Discussion with @philhewinson lead to some ideas around gamification. Perhaps the best of these is a format inspired by Who Wants to Be a Millionaire?:
Multiple (but finite) levels. At each level, the user is prompted to select their favourite, or rather which they think is the most popular glyph from a particular emoji. If they choose correctly they move to the next level. Difficulty of levels can be calculated by variance in glyph_score.
Big problem with this approach: all the data (i.e. answers) are available on the emoji pages.
The text was updated successfully, but these errors were encountered: