This is a wireframe slide show of 3 different sample user cycles. Above each frame I'll add notes. Below you see the general template with timers on the left. The timers are counting down in seconds. The top timer on the left is for the active screen, and the other small timers below it are the amount of time until a new page comes along. Throughout the wireframes these do not really change, but in the actual scenarios, those would constantly be counting down.
User 1 decides to start a derby. He adds a picture. I did not add the button on this page for starting a new derby. That button will be needed. After this user's time runs out, the picture automatically goes to the next person in the derby.
Here we see the screen that User 2 creates. Also notice that the original image sent is now the first thumbnail on the right. Here is user 3's addition. Again, notice the thumbs accumulating on the right. These can be rolloed over and the thumb enlarges. if the user woudl like to revert back to one of these versions, he will need to do a screenshot when it's enlarged, and then mess with that screenshot in photoshop or something, and then upload the new image. User 4's addition. User 5's addition And lastly, User 6 gets a final crack at the image. He can then send it around, or it gets saved in his profile, along with each version that led to the final version. Participants are attached to their versions. The database within user profiles can then either be private or public, and in either case they can be tagged and the database can be searched for keywords. This is the first screen of the second example, or cycle. This first screen is intended to illustrate that users can simply chat if they want to, but when they send it off into the derby, there's no telling what will happen. User 2 in "the deb cycle" simply continues the chat. User 3 continues the chat, but adds some color and boxes around her writing. User 4 notices a face in the chat and follows his inspiration. Maybe he doesn't know who Deb is, whatever the case, this is what he's chosen to contribute. Here we notice the final step in the cycle which means it is the original sender, and he adds Deb Forever, yellow background, bloodshot eyes and some gold teeth. This third example is meant to show how users can start these chat derbies with what might be seen as an implied parameter. Perhaps this is a derby where the user chose only friends to play along so as to avoid randomness. (Two options, random grouping of friends to receive the derby, and also choosing friend circles.) User 2 clearly took the block theme and added his pink flavor. User 3 in this sequence added her green highlights. User 4 did not add blocks, but instead highlights. we don't know if this made the original sender angry. these are ficitional wireframes. here we have the last user who has tried to create a sort of black fountain going through the three dimensionality of part of the structure. so, clearly this string of images would be tagged with things like, "blocks," "play," etc. second design pass