On Thu, 2010-08-05 at 12:08 +0200, david blanchard wrote:
> First draft of use cases here ->
> http://community.hackit.cx/wiki/Usecases_%26_mockups

Wow, very nice work! It's much better now : ) It's also bigger, so it
will require more development time this way, but it's not a bad thing
here I think - the smaller version without the management screen would
have be quicker to develop, but depending on how it would have been
coded, adding the management screen later on could have been harder.

So I like it this way : )

> Please let me know what's missing.

A few comments:

      * Need to explicitly say that a player clicking on a link to join
        or see a game through a wall post should go directly to the game
        (not the main screen to create games)
      * Anyone, not only invited players, should be able to join (so
        there is no need to cancel invitations - see my mockup 5 to see
        how this can be done with open invitations), or simply watch the
        game without playing it. The general idea is to favor parties
        with more people, rather than relying on the organizer's choice
        (we don't want to turn down a new player trying to join a game),
        and try to make it an activity on the wall, something that will
        make people talk and interact directly on the wall, not just a
        mere advertisement like most facebook games notifications.
      * For the invitations, the two-step process may be confusing for
        users - I'd rather use the full list directly
        
http://facebook-developer.net/wp-content/uploads/2008/02/invite-form-output.jpg 
(except that we would post on the user's wall in addition to sending the 
standard game invitation/request, which are very hidden on Facebook now). 
Displaying only the list of players who already play the game is good for the 
leaderboard, but to invite people it would be better to display the full list 
of friends directly, to give more incentive to invite new players
      * To force people to "publish" the results (and thus advertise the
        game), the other players shouldn't be able to see the results
        unless the GM published them on his wall, even if everyone has
        voted and they go back to the game - it should say "waiting for
        the organizer to publish the results", and it needs to be
        explicitly mentioned in the specs imho
      * Need to find a better name for organizer, a nice title that will
        give value to that role - it's an important role, they are the
        ones who will spread the application. What about "narrator", or
        "author"?
      * Need to add email notifications (new game, turn, automated
        reminders when players don't play, publication of results...)
      * Need to list the information we want to retrieve from the
        players facebook account and store on our servers (email, name,
        sex, age, location, favorites, etc.)
      * There are too many cards to chose from for the player I think -
        it makes sense to give a lot of them to the organizer (otherwise
        he could just create games until he gets the card he wants), but
        the choice of players should be more limited IMHO, otherwise it
        will be too easy to match the card of the organizer, and we'll
        burn the content more quickly.
      * It would be good to add some tips and a general explanation of
        the game on the screens, especially on the players screens. We
        don't need a tutorial at this stage, but I think the players
        need to be able to get the general idea if they want to - the
        explanation should be brief, and the player shouldn't feel that
        he has to read it, but it can be hard to play if you don't know
        the goal.
      * Would be good to have the button "Create another game" on both
        the player and organizer screens, as an incentive to keep
        playing once a game is finished
      * Need to have a unique URL for each game, accessible publicly
        (opens the possibility to add non-FB sharing features more
        easily later on)
      * Missing technical requirements (to take from Hackit, and add to
        that that:the implentation should follow the Facebook guidelines
        and advices found on http://developers.facebook.com/ , and use
        the Graph API http://developers.facebook.com/docs/api  ).
      * We should add one-click action buttons to bookmark and Like the
        application, in a preeminent place on every single page (and
        make it disappear when players do the action)

Cool btw - looks like we should be able to post this on RaC this
week : ) Can't wait to see how it goes!

Xavier.

_______________________________________________
Hackit Bar mailing list - [email protected]

Wiki:  http://community.hackit.cx/
List:  http://community.hackit.cx/ml/
Forum: http://community.hackit.cx/forum/
Ideas: http://community.hackit.cx/ideas/
IRC:   irc://irc.freenode.net/#politis

Reply via email to