This is very very late, I know. Planned to do it right after the lecture, but never manage to write even a draft ‘cuz there’s too much work (and entertainment) going on. This is Friday night/Saturday morning and I’m writing this, kinda weird hehe.
Most of the points we discussed on the GetHelp case, I’ve already mentioned in my previous post. Just some quick summary again:
- Keep the design simple, easy to use.
- Motivation for user to use the app.
- Provide some kind of helps for dummy users (there’re a lot of them).
- Kent, please stop the annoying notification. Not only it slows down your app (I have 400+ friends = 400+ API calls for every new request, good luck with that), but also it’s super annoy when people receive random notifications.
More on the UI thing, you guys can borrow the book “Designing for the social web” – Joshua Porter. It’s available on Central Lib, pretty solid book for social web design. If you read the book carefully, you would like to borrow another one. I’m holding to that one, so I won’t disclose the name :-P, you must find out yourself. The Joshua’s book is excellent (in my opinion), it describes very details what factors you should consider before you design a social website (both UI and content). HIghly recommend :P.
The team dynamic case was very interesting. The thing is I has always faced the same thing for most of my project in NUS so far. It gave me a better approach to a teamwork problems, especially when you are in big big team. If only we had more time, I would love to hear more from Ben and Vincent about their experiences..
Can you send me the name of the other book? Dun worry, won’t snatch from you. Will buy a copy for my own reference. :-)
Can you send me the name of the other book? Dun worry, won’t snatch from you. Will buy a copy for my own reference. :-)
I think he’s referring to “Inside Steve’s Brain” haha
@huytoan: Nope :P